Updates OTEL version to v0.101.0.

[StefanKurek]

PR Description

Updates vcenterreceiver and its many bug fixes and updates for use by Alloy. Updates probabilisticsampleprocessor to use new failed_closed config.

Which issue(s) this PR fixes

N/A

Notes to the Reviewer

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[wildum]

Hi, thanks for your contribution! We update our Otel dependency before every Alloy release in one go to make sure that we reflect all otel changes in our components. If you don't mind, could we merge your branch to the update-otel-v0.101.0 instead of main? I would then use your changes as a start to update the rest of the otel components

[StefanKurek]

Hi, thanks for your contribution! We update our Otel dependency before every Alloy release in one go to make sure that we reflect all otel changes in our components. If you don't mind, could we merge your branch to the update-otel-v0.101.0 instead of main? I would then use your changes as a start to update the rest of the otel components

@wildum No problem. I wasn't sure if this was the case as I noticed with the recent release OTEL was still at v0.99.0 vs 0.100.0. I just wanted to get ahead of this as I'm working on the Grafana integration for vSphere, so I've first been doing the work on the OTEL receiver for vCenter. Now I'll be shifting my work to Grafana's jsonnet-libs and cloud-onboarding repos.

Also, hopefully there isn't too much else to do. I tried to look at the release notes for v0.100.0 and v0.101.0 and see what components in Alloy had updates. I "think" I hit what needed to be done in this PR? I could be wrong though...

[wildum]

Also, hopefully, there isn't too much else to do. I tried to look at the release notes for v0.100.0 and v0.101.0 and see what components in Alloy had updates. I "think" I hit what needed to be done in this PR? I could be wrong though...

Hey you are right actually, sorry I usually expect many more changes when we upgrade our otel dependency but I just went through the release notes and it looks like you did all the changes! That's really super helpful, I will review your code and then we will merge it to main directly

[wildum]

Seems like changing the default value to true is making some tests fail. I can take a look at it on Monday

[StefanKurek]

Seems like changing the default value to true is making some tests fail. I can take a look at it on Monday

@wildum digging into it a bit more, the new config field refuses data when randomness cannot be determined from the log/trace (which was the case in these test conditions). I fixed them.

[wildum]

Thanks for fixing the tests :) When you have time, can you update the changelog and rebase with main? I will then merge the branch

[wildum]

Merged, thanks again @StefanKurek !