Release v1.50.0/v0.144.0

[github-actions]

Like #14236, but for v1.50.0/v0.144.0
Performed by collector release manager

• [chore] Prepare release v1.50.0/v0.144.0 #14451
• Tag and release core v1.50.0/v0.144.0

Performed by collector contrib release manager

• [chore] Prepare release 0.144.0 opentelemetry-collector-contrib#45517
• Tag and release contrib v0.144.0

Performed by collector releases release manager

• [chore] Prepare release 0.144.0 opentelemetry-collector-releases#1348
• Tag and otelcol containers images release v0.144.0

Performed by operator maintainers

• Release the operator v0.144.0 opentelemetry-operator#4654

Performed by helm chart maintainers

• Update the opentelemetry-collector helm chart to use v0.144.0 opentelemetry-helm-charts#2049

[mx-psi]

There was a minor issue on the binary release open-telemetry/opentelemetry-collector-releases/issues/1350. We are discussing whether this warrants a bugfix release or not (and appreciate feedback on that topic on the issue)

[gimsesu]

Hi maintainers,

I noticed that the changes from this PR(#13663) appear to be included in v0.144.0 (I verified by checking the actual source code), but there's no mention of it in the release notes.

I suspect the changelog entry might have been missed during the PR process. Could you please advise on the proper procedure in this case?

1. Should a changelog entry be retroactively added to the release notes?
2. Is there a specific process for documenting changes that were merged without a changelog entry?

This change (DialContext → NewClient migration) could affect users relying on gRPC connection behavior, so it would be helpful to have it documented.

Thanks!

cc @sivchari

[dmathieu]

This PR has no changelog entry because it was deemed a non user-facing change, as it should only be a move out of a deprecated method.
If you believe there are more impactful changes, could you open an issue describing the impact there could be ("connection behavior" is a bit short)?