enhancement: support proto resources for grpc-transcode workflows

[kayx23]

Summary

Please triage whether the controller should support managing proto resources needed by grpc-transcode workflows.

Current behavior

APISIX itself supports proto resources for grpc-transcode through the Admin API, including proto_id references from route plugin configuration, but the current controller API surface does not provide a resource model for defining and delivering those proto descriptors.

The codebase includes grpc-transcode in the runtime plugin set, but there is no corresponding CRD or Gateway API abstraction for proto resource management.

As a result, a grpc-transcode setup that works in APISIX cannot currently be expressed end-to-end through the controller.

Use cases affected

• configuring grpc-transcode end-to-end through the controller, including both the route/plugin configuration and the proto descriptor it depends on
• managing proto descriptors declaratively alongside routes and upstreams, instead of falling back to a separate manual configuration path

Code context

• api/ currently does not expose a proto resource model for this workflow
• the e2e manifests include grpc-transcode in the runtime plugin set, but not a controller resource for proto definitions

[coderabbitai]

🔗 Related PRs

#387 - feat: support skip gatewayapi v1alpha2 [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!