Collector: init memory allocation investigation, need to upgrade ottl

[maxday]

Similarly to #1827, I noticed that ottl init phase is responsible for quite some overhead in time and memory allocation.

init github.com/open-telemetry/opentelemetry-collector-contrib/pkg/ottl @4.9 ms, 2.4 ms clock, 1965848 bytes, 13390 allocs

As you can see it this memory profile, those allocation are from the parser initializations. I created a PR upstream to fix it by initialization them on demand, this way users won't pay the overhead at cold start if they're not using it.
Link to the upstream PR: open-telemetry/opentelemetry-collector-contrib#40254

This issue is created to track the progress on the upstream PR and not to forget to bump the dependency is merged/released.

[maxday]

upstream PR has been approved :) and should be merged soon

[maxday]

upstream PR has been merged, will follow-up with bumping when it will be released