Add symfony/ai-*-store recipes

[OskarStark]

Q	A
License	MIT
Doc issue/PR	--

[github-actions]

Thanks for the PR 😍

How to test these changes in your application

1. Define the SYMFONY_ENDPOINT environment variable:

   # On Unix-like (BSD, Linux and macOS)
   export SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes/flex/pull-1503/index.json
   # On Windows
   SET SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes/flex/pull-1503/index.json

2. Install the package(s) related to this recipe:

   composer req symfony/flex
   composer req 'symfony/ai-azure-search-store:^0.1' 'symfony/ai-bundle:^0.1' 'symfony/ai-cache-store:^0.1' 'symfony/ai-chroma-db-store:^0.1' 'symfony/ai-click-house-store:^0.1' 'symfony/ai-cloudflare-store:^0.1' 'symfony/ai-elasticsearch-store:^0.1' 'symfony/ai-manticore-search-store:^0.1' 'symfony/ai-maria-db-store:^0.1' 'symfony/ai-meilisearch-store:^0.1' 'symfony/ai-milvus-store:^0.1' 'symfony/ai-mongo-db-store:^0.1' 'symfony/ai-neo4j-store:^0.1' 'symfony/ai-open-search-store:^0.1' 'symfony/ai-pinecone-store:^0.1' 'symfony/ai-postgres-store:^0.1' 'symfony/ai-qdrant-store:^0.1' 'symfony/ai-redis-store:^0.1' 'symfony/ai-supabase-store:^0.1' 'symfony/ai-surreal-db-store:^0.1' 'symfony/ai-typesense-store:^0.1' 'symfony/ai-weaviate-store:^0.1'

3. Don't forget to unset the SYMFONY_ENDPOINT environment variable when done:

   # On Unix-like (BSD, Linux and macOS)
   unset SYMFONY_ENDPOINT
   # On Windows
   SET SYMFONY_ENDPOINT=

Diff between recipe versions

In order to help with the review stage, I'm in charge of computing the diff between the various versions of patched recipes.
I'm going keep this comment up to date with any updates of the attached patch.

[fabpot]

I would add a small comment to help user understand what should be part of store and maybe hint at the recipes?

[OskarStark]

It is done in the other PR from @chr-hertel

[stof]

If the order of stores is not relevant (and I don't think it is), I would suggest using separate files for each bridge to provide the semantic configuration instead of those add-lines rules for the ai.yml file. This has several benefits:

• it will have better support for the recipes:update command, but relying on the git merge algorithm instead of hoping to be able to patch files
• it will be more robust (add-lines rules can break in case the dev has edited the file and changed the part used as marker)
• it will be more readable in this repo where we have tooling to compare files (and no tooling to validate or compare add-lines rules)

[chr-hertel]

@OskarStark needs a rebase now