feat(elasticsearch): OpenSearch support

[hotfix31]

Q	A
Branch?	main
Tickets	#7519
License	MIT
Doc PR	api-platform/docs#2259

Hello,

Following up on #7519 — here's my take at adding OpenSearch support to the Elasticsearch bridge.

Given how similar the two clients are, it felt much simpler to patch the existing bridge rather than create a separate bundle that would have been little more than a copy with very little added value.

The idea is pretty simple: a new client option under api_platform.elasticsearch that accepts either "elasticsearch" (default, nothing changes) or "opensearch". When set to "opensearch", the bridge uses opensearch-project/opensearch-php instead of the Elasticsearch client. The package is declared as a suggest so it stays fully optional.

On the code side, ElasticsearchClientPass builds the client through OpenSearch\ClientBuilder::fromConfig when configured, and both CollectionProvider and ItemProvider now accept OpenSearch\Client and catch its Missing404Exception. The rest is config wiring and validation.

Configuration looks like this:

api_platform:
    elasticsearch:
        enabled: true
        client: opensearch
        hosts:
            - '%env(OPENSEARCH_URL)%'

CI-wise I added a PHPUnit matrix entry running the elasticsearch component tests with pensearch-php installed, plus a Behat job against an OpenSearch 2.19.4 container. Everything is green and existing Elasticsearch tests are unaffected. Full transparency: I'm not very familiar with GitHub Actions so Claude Code helped me a lot on that part.

Happy to adjust anything based on your feedback!

Fred

[soyuka]

wow really nice addition! Thanks!