deps: update rules_proto to v5.3.0

[malt3]

Upstream release: https://github.com/bazelbuild/rules_proto/releases/tag/5.3.0-21.7

Proposed change(s)

• update rules_proto to v5.3.0

Related issue

• Upstream PR to use hermetic / statically linked protoc

Additional info

• Breaks build on NixOS since protoc is not hermetic.
• We should not merge this and instead upgrade to the next release with static protoc.

Checklist

• Update docs
• Add labels (e.g., for changelog category)
• Link to Milestone

[netlify]

✅ Deploy Preview for constellation-docs canceled.

Name	Link
🔨 Latest commit	4b215e9
🔍 Latest deploy log	https://app.netlify.com/sites/constellation-docs/deploys/63edfe054bd65e00087e2f15

[malt3]

We need to wait for the next release of rules_proto, so the protoc binary is statically linked. See this failed attempt: bazelbuild/rules_proto#168

What's really missing is for rules_proto and protobuf to gain upstream bzlmod support, so they can actually release new versions. TL:DR: We are blocked on protocolbuffers/protobuf#14564

[malt3]

rules_proto has a new toolchain design and new releases do ship with statically linked protoc: https://github.com/bazelbuild/rules_proto/releases/tag/6.0.0

However, upgrading is still blocked by other dependencies not being compatible with this new major version of the ruleset.

This was one of the issues I observed when trying to upgrade:

bazelbuild/rules_proto#212