Consider publishing grpc-gateway to Bazel Central Registry

[hharrisd]

We maintain an SDK that depends on grpc-gateway. We're encountering challenges with Bazel's module system, as override directives only work in root modules.

Publishing grpc-gateway to BCR would:

• Eliminate the need for overrides
• Ensure consistent builds across all dependent projects
• Reduce maintenance overhead for downstream users
• Align with Bazel's recommended dependency management practices

We're willing to help with the BCR publication process if you're interested. Would you consider this addition to improve the experience for grpc-gateway users?

[johanbrandhorst]

Thanks for your issue. We've talked about doing this before so it's definitely something I'd consider. Please feel free to open a PR. I want to make sure this doesn't unduly add to the maintenance burden of this repository, so I'd want publishing to the registry to happen automatically when a new release is built. I'm happy to registry any accounts and populate secrets necessary for CI. CC @AlejoAsd who helped add our bzlmod support.