[Bazel] Update bazel module to use jetty release branches

[iche033]

🦟 Bug fix

Summary

Change main to jetty release branches

Checklist

• Signed all commits for DCO
• Added tests
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• While waiting for a review on your PR, please help review another open pull request to support the maintainers
• Was GenAI used to generate this PR? If so, make sure to add "Generated-by" to your commits. (See this policy for more info.)

Generated-by: Remove this if GenAI was not used.

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by and Generated-by messages.

[azeey]

It's not great that we have another place to maintain these branch names. It would be nice if we can automate this somehow to pull from gazebodistro. Maybe a script in release-tools to update these files?

[scpeters]

It's not great that we have another place to maintain these branch names. It would be nice if we can automate this somehow to pull from gazebodistro. Maybe a script in release-tools to update these files?

this is a big topic, perhaps move to an issue or the infra slack?

[iche033]

It's not great that we have another place to maintain these branch names. It would be nice if we can automate this somehow to pull from gazebodistro. Maybe a script in release-tools to update these files?

this is a big topic, perhaps move to an issue or the infra slack?

I ticketed an issue for this: gazebo-tooling/release-tools#1386

[azeey]

Yes, I agree it's a bigger topic. Thanks for creating the release-tools issue!

[iche033]

ok merging this PR first.