[chore] Prepare release v1.56.0/v0.150.0

[otelbot]

The following commands were run to prepare this release:

• make chlog-update VERSION=v1.56.0/v0.150.0
• make prepare-release PREVIOUS_VERSION=1[.]55[.]0 RELEASE_CANDIDATE=1.56.0 MODSET=stable
• make prepare-release PREVIOUS_VERSION=0[.]149[.]0 RELEASE_CANDIDATE=0.150.0 MODSET=beta

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.23%. Comparing base (5d7304d) to head (0addac4).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #15101      +/-   ##
==========================================
- Coverage   91.24%   91.23%   -0.01%     
==========================================
  Files         699      699              
  Lines       44758    44758              
==========================================
- Hits        40840    40837       -3     
- Misses       2775     2777       +2     
- Partials     1143     1144       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dmathieu]

The contrib update job that @andrzej-stencel triggered this morning seems to fail.
https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/24331106236/job/71036958097

However, contrib was updated with the latest code commit on friday, and the only non-doc commit after that is 5d7304d (semconv bump).
So I believe this should be good to go.

[mx-psi]

The contrib update job that @andrzej-stencel triggered this morning seems to fail. https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/24331106236/job/71036958097

However, contrib was updated with the latest code commit on friday, and the only non-doc commit after that is 5d7304d (semconv bump). So I believe this should be good to go.

Visiting the failing URL on my browser seems to work now so I think this was a transient failure