[pkg/ottl] Consider support of dynamic keys in OTTL functions

[odubajDT]

Component(s)

pkg/ottl

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

In the current state, some OTTL function have the support of dynamic keys, some don't and there actually isn't a rule for these decisions. We have a regular feature requests like here, for support. Let's think ahead and support the dynamic keys where it makes sense.

Describe the solution you'd like

Potentially all OTTL functions should support dynamic keys, for start I would propose the following:

• Concat()
• Decode()
• ExtractGrokPatterns()
• ExtractPatterns
• HasPrefix()
• HasSuffix()
• IsMatch
• Split()
• keep_keys
• keep_matching_keys()
• replace_all_matches()
• replace_all_patterns()
• replace_match()
• replace_pattern()

Describe alternatives you've considered

No response

Additional context

related to #43081

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[github-actions]

Pinging code owners:

• pkg/ottl: @TylerHelmuth @evan-bradley @edmocosta

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[edmocosta]

I support it, but let's split it into individual PRs per function. If someone is interested on helping with that, please claim the function you would like to change here.

We also need to ensure that the performance of those functions are not considerably affected (benchmarking it), and that #40222 is being used wherever it makes sense.