Use matching branch names for Prs created from prepare release workflow

[lzchen]

Is your feature request related to a problem?

For PRs that are created automatically as part of the prepare-release-branch.yml workflow, we use specific release branch names. As part of making the tests pass, maintainers must manually update the SHA. Investigate the possibility of using specific branch names so we can change the SHAs programatically as part of the prepare-release workflow instead of having to change it manually. One PR will most likely fail due to the corresponding branch in the other repo might not be created yet, but a simple rerun should most likely make builds pass.

Describe the solution you'd like

.

Describe alternatives you've considered

No response

Additional Context

No response

Would you like to implement a fix?

None

[aabmass]

For clarity, this is about the core and contrib repo PRs and making those SHAs match

[aabmass]

One issue with this (and using main instead of a SHA in the main branch) is that the build is not reproducible in the future as branch pointer moves vs using an actual commit SHA. It would be nice to have hermetic builds.

Discussed with maintainers and this is still great first step to get a baseline of frictionless releases.

[xrmx]

Tried to took a stab this without much luck https://github.com/xrmx/opentelemetry-python/actions/runs/12012704653