Describe the bug

Brief introduction
The Elasticsearch 7 Docker configuration examples are missing the required property:

conductor.indexing.type=elasticsearch

Without this property, Spring does not create the ES7 IndexDAO bean, and server startup can fail with a missing IndexDAO error.

Details
Conductor version: current main
Persistence implementation: reproduced with MySQL
Queue implementation: Redis
Lock: Redis
Workflow definition: N/A
Task definition: N/A
Event handler definition: N/A

To Reproduce

1. Clone the repository
2. Run:

   docker compose -f docker/docker-compose-mysql.yaml up --build

3. Wait for conductor-server startup
4. Observe failure similar to:

   Parameter 2 of constructor in com.netflix.conductor.core.dal.ExecutionDAOFacade required a bean of type 'com.netflix.conductor.dao.IndexDAO' that could not be found.
   

Expected behavior
The ES7 Docker examples should start successfully and create the Elasticsearch-backed IndexDAO.

Additional context
The issue was reproduced with the MySQL example, but the same missing property also exists in other ES7-backed Docker config files:

• docker/server/config/config-mysql.properties
• docker/server/config/config-redis.properties
• docker/server/config/config-postgres-es7.properties

The docs/examples for Elasticsearch 7 also omit the same property, which makes the configuration guidance incomplete.

Root cause:

• ES7 conditional configuration requires conductor.indexing.type=elasticsearch
• the Docker ES7 configs set conductor.indexing.enabled=true and conductor.elasticsearch.version=7
• but the conductor.indexing.type=elasticsearch property is not set
• as a result, no IndexDAO bean is created

Proposed fix:

• add conductor.indexing.type=elasticsearch to all ES7 Docker config files
• update the docs to include the required property
• add a regression test for the ES7 conditional activation