[bazel] Update MODULE.bazel

[shameekganguly]

🦟 Bug fix

Summary

Few small fixes in MODULE.bazel as pre-work to add automation to push new releases to BCR.

• Remove archive_override for gz-utils dep and used Jetty package from BCR instead. As a result, bazel CI will use released versions of gz deps, which is consistent with cmake CI.
• Drop repo_name, which removes the need to patch MODULE.bazel when pushing a release to BCR. repo_name is not a required field and can be added on the client side during import if needed to disambiguate packages.
• Add back buildifier rules to keep bazel files formatted consistently. This also requires importing cc_* rules from rules_cc since native repo rules will be flagged as warning in bazel 8 and dropped completely in bazel 9.

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.)

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.

[scpeters]

I didn't include this in the cherry-pick forward to main in #699 since it changes the gz-utils dependency to a tarball rather than building from main. Do you think the other changes are separable?

[shameekganguly]

I didn't include this in the cherry-pick forward to main in #699 since it changes the gz-utils dependency to a tarball rather than building from main. Do you think the other changes are separable?

@scpeters I created a manual forward port in #700 since we want to keep using gz deps from HEAD on the main branches for CI.