Bump OTLP to v1.7.0 and handle malformed OTLP profiles

[fandreuz]

Fixes #4220, and reintroduces the changes from #4212.

In addition to #4212, this has two more commits:

• 8814dcf: graceful error handling for malformed OTLP data
• b8b03cd: new tests with malformed data

[kolesnikovae]

Thank you @fandreuz for adding this!

It looks very good overall, and I'm going to review it carefully tomorrow. @korniltsev, if you get a chance, it would be great if you could take a look as well

[kolesnikovae]

Thank you for all the effort, @fandreuz – it looks great! We'll dogfood some real OTLP profiles over an extended period and plan to merge it next week.

[fandreuz]

Hi @kolesnikovae, I noticed Pyroscope enforces the presence of a mapping for each location. According to the spec, that field is optional. Profiles not carrying it should probably be accepted without errors.

I'll fix the merge conflicts later today

[simonswine]

Thank you for your contribution! I have been running this against the latest otel-ebpf-profiler and works like a charm.

LGTM

[simonswine]

Hi @kolesnikovae, I noticed Pyroscope enforces the presence of a mapping for each location. According to the spec, that field is optional. Profiles not carrying it should probably be accepted without errors.

@fandreuz This in fact will change with the next version, as very recently some PR marked this as no longer optional. But feel free to follow up with another PR