Allow configuring the CamundaExporter

[deepthidevaki]

Most configurable parameters are already added as part of the respective PRs that add the feature. But there might be missing ones. This issue is to review and add any necessary configuration.

• Refactor exporter config #23198
• Review what is configurable in Operate and if we need to port this
• Review currently implemented properties and if we should consolidate them.
• Add validations for the configuration if applicable
• Provide the config to enable the Exporter in the Helm charts - see [ENHANCEMENT] Execution Identity integration - iteration 2 camunda-platform-helm#2294
• Provide the config to enable the Exporter in the SaaS controller - see https://github.com/camunda-cloud/camunda-operator/issues/3258

[mustafadagher]

I reviewed the configuration used in Operate as much as my knowledge could help (and in zeebe exporters too), and I couldn't find any configs that we missed except for two main things that exist in zeebe elastic search exporter

1. indexSuffixDatePattern and I don't think we need this one now, unless you think otherwise.
2. bulk.memoryLimit which we have now, yet left unused and I'll delete it according to the discussion in CamundaExporter should respect the memory limit in bulk configuration too when batching exported records #22869

I'll open a PR in a bit with some config validations that are ported from zeebe (I couldn't find anything relevant in operate code base).

EDIT: Operate also uses a refreshInterval in the indexSettings, I don't know if we should have this in the exporter as well.

@sdorokhova please advise if you see something that I might have missed.

[sdorokhova]

EDIT: Operate also uses a refreshInterval in the indexSettings, I don't know if we should have this in the exporter as well.

@sdorokhova please advise if you see something that I might have missed.

I don't think that we need it.

Going over Operate code, it looks like we use it only in migration, which we won't have.