Do upgrade testing 1.1.0 with possible combinations

I will set it as release blocker, however the "normal" upgrade path is tested and it is the most important. We will have RC before stable as well.

Tried test setup. Assuming the Milvus Provider in step 2 is 1.0.0-beta2. Completed till step 16, On adding a new view with the index, got an error

The submitted value search_api_data in the output as element is not allowed.
The submitted value search_api_data in the Feed row style element is not allowed.

This might be related to core issue https://www.drupal.org/project/facets/issues/3446040 🐛 The submitted value [value] in the [name] element is not allowed. Active

After upgrading the AI module to 1.1.x-dev, Faced a fatal error:

Fatal error: Declaration of Drupal\ai_vdb_provider_milvus\Plugin\VdbProvider\MilvusProvider::vectorSearch(string $collection_name, array $vector_input, array $output_fields, mixed $filters = '', int $limit = 10, int $offset = 0, string $database = 'default'): array must be compatible with Drupal\ai\AiVdbProviderInterface::vectorSearch(string $collection_name, array $vector_input, array $output_fields, Drupal\search_api\Query\QueryInterface $query, string $filters = '', int $limit = 10, int $offset = 0, string $database = 'default'): array in /var/www/html/modules/contrib/ai_vdb_provider_milvus/src/Plugin/VdbProvider/MilvusProvider.php on line 597

This is mentioned in https://www.drupal.org/project/ai/issues/3515861 🐛 MilvusProvider.php on line 597 Active .

@marcus_johansson Kindly let me know the milvus db provider version to be used for testing. in test setup it is mentioned "Milvus Provider 1.0.2-beta2" . But there is no version 1.0.2-beta2 available. Currently I have used "1.0.0-beta2"

Oh, sorry - the update of any VDB provider has to be 1.1.x. This should be automatic on release, see: https://www.drupal.org/project/ai_vdb_provider_milvus/issues/3528067 📌 Pin version 1.0.0 to AI 1.0.x Active

In Test #1:

4. Try to add an article with the CKEditor assistants tools and Content Suggestions.

Result: Unable to get response from ai when using CKEditor assistants "Story teller" created in test setup step 13. Story teller was working correctly before update. However summarize plugin from ckeditor module and summarize in content suggestions works perfectly. error in story teller automator chain:
InvalidArgumentException: Field selected_text is unknown. in Drupal\Core\Entity\ContentEntityBase->getTranslatedField() (line 617 of /var/www/html/core/lib/Drupal/Core/Entity/ContentEntityBase.php).

5. successfully translated article node with ai translate.
6. On creating any new content/translation, the node is getting indexed.
7. was unable to create view in test setup. So Unable to test step 7.
8. Successfully created test automators by filling in only title field and long string generated from AI.
9. Response from chatbot:

The content types available on this Drupal instance are:

    Article
    Basic page
    Test Automators

10,11,12,13: Visited the paths and no error observed
14, 15: Unable to access the path. Fatal error:

The website encountered an unexpected error. Try again later.

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "ai_agent" entity type does not exist. in Drupal\Core\Entity\EntityTypeManager->getDefinition() (line 139 of core/lib/Drupal/Core/Entity/EntityTypeManager.php). 

16,17: Visited the paths and no error observed
18, 19: No errors observed

First follow up issue 🐛 Only show agent assistant form, if AI Agents 1.1.x+ is available Active

Second follow up issue 🐛 AI Automators CKEditor plugin is broken Active

In test #2: observed results are similar to that observed in test #1. Completed testing.

4. Unable to get response from ai when using CKEditor assistants "Story teller" created in test setup step 13. Already reported in the above comment https://www.drupal.org/project/ai/issues/3528446 🐛 AI Automators CKEditor plugin is broken Active and fixed.

summarize plugin from ckeditor module and summarize in content suggestions works perfectly.

5. successfully translated article node with ai translate.
6. On creating any new content/translation, the node is getting indexed.
7. was unable to create view in test setup. So Unable to test step 7.
8. Successfully created test automators by filling in only title field and long string generated from AI.
9. Obtained correct response from chatbot.
10,11,12,13: Visited the paths and no error observed
14,15,16,17: Visited the paths and no errors observed.
18, 19: No errors observed

Retested and found no issues other than those reported above.