Elasticsearch to Opensearch migration

[Junjiequan]

Investigation Summary Elasticsearch to Opensearch ( 1 day time boxed )

Based on the investigation:

1. No elasticsearch specific or only features are used. Only minor API differences are expected due to the client library change.

2. The current indexing strategy is basic and compatible with opensearch

3. Existing queries (partial search, filtering, aggregations, sorting) are supported by opensearch

4. A full re-index and data re-synchronization will be required, as we are migrating from Elasticsearch 8.8.1 to Opensearch 3.5.0 (latest) and index formats are not guaranteed to be compatible.

Next steps:

1. Replace the Elasticsearch client with the Opensearch client

2. Replace the Elasticsearch docker image with Opensearch for local development and CI.

BE:

CI/E2E/docker-compose.yaml 
CI/E2E/docker-compose-local.yaml
CI/ESS/docker-compose.api.yaml
CI/ESS/docker-compose.yaml

FE:

CI/e2e/docker-compose.e2e.yaml 

3. Update Elasticsearch service code to accomodate Opensearch API and type differences.

4. Update Elasticsearch tests accordingly

5. All the change should remain in the feature branch untill the migration is fully validated

Nice to have:

1. Remove the scientificMetadata field from search queries, as dynamic value type mappings for this field cause unreliable behavior in both Elasticsearch and Opensearch