Is the @type elasticsearch_dynamic supported by fluent-operator ?

### Is your feature request related to a problem? Please describe.

https://github.com/uken/fluent-plugin-elasticsearch
Dynamic configuration
NOTE: out_elasticsearch_dynamic will be planned to be marked as deprecated. Please don't use the new Fluentd configuration. This plugin is maintained for backward compatibility.

If you want configurations to depend on information in messages, you can use elasticsearch_dynamic. This is an experimental variation of the Elasticsearch plugin allows configuration values to be specified in ways such as the below:

@type elasticsearch_dynamic
hosts ${record['host1']}:9200,${record['host2']}:9200
index_name my_index.${Time.at(time).getutc.strftime(@logstash_dateformat)}
logstash_prefix ${tag_parts[3]}
port ${9200+rand(4)}
index_name ${tag_parts[2]}-${Time.at(time).getutc.strftime(@logstash_dateformat)}

### Describe the solution you'd like

It would be nice to have logs end up in different indices based the namespace

### Additional context

_No response_

Start by reviewing how fluent-operator represents and validates Elasticsearch output configuration, then compare it with the fluent-plugin-elasticsearch `elasticsearch_dynamic` examples in the issue. Determine what support is needed for namespace-dependent indices and how completion can be verified through the operator's existing configuration or integration tests.

Written by the indexing model from the issue text.