enhancement: support route label propagation for Gateway API resources

[kayx23]

Summary

Please triage whether the controller should support propagating user-defined route labels when using Gateway API resources.

Current behavior

The current controller appears to preserve object labels for ApisixRoute, but I did not find equivalent propagation for Gateway API route resources such as HTTPRoute.

This means route label based usage patterns available through the APISIX CRD path may not carry over to the Gateway API path.

Use cases affected

• using route labels to drive global-plugin logic or other label-based management workflows
• keeping Gateway API route metadata aligned with the label propagation behavior available on the APISIX CRD side

Code context

• internal/adc/translator/apisixroute.go
• internal/adc/translator/httproute.go

[coderabbitai]

🔗 Related PRs

#417 - fix: omit uris field when HTTPRoute path type is RegularExpression (backport apache/apisix-ingress-controller#2770) [closed]
#418 - fix: update observedGeneration on Gateway-API route status conditions (apache/apisix-ingress-controller#2768) [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!