[ENHANCEMENT] simpler Optimize configuration (when using custom Elasticsearch index prefix)

[bbakker2]

Describe the use case:

We use custom Elasticsearch index prefixes. The helm chart does not provide properties to set the zeebe-record or the optimize index prefixes. Optimize also does not appear to support the springboot configuration mechanism to override configuration keys with environment variables, like Operate and Tasklist do. Consequently we have to put the configuration in optimize.configuration. This adds redundancy to the helm values.yaml and exposes Optimize configuration internals (e.g. like having to set spring.profiles.active: ccsm

Describe the enhancement/feature: Either add helm chart values for Optimize for config options.

• zeebe.name. Even better: let it use global.elasticsearch.prefix as default.
• es.settings.index.prefix

or add support for environment variable based configuration overrides to Optimize.

Additionally, for consistency it would be great to have optimize use zeebe.partitionCount instead of having to configure it manually.

You can configure Optimize without having to specify the full optimize.configuration.

[aabouzaid]

It will be fixed by https://github.com/camunda/camunda-platform-helm/issues/2186