As a platform engineer, I want to manage TokenRateLimitPolicy resources through the OpenShift Console Plugin UI so that I can easily view, create, and edit token policies without needing to work directly with raw YAML.

This story introduces native support for TokenRateLimitPolicy in the OpenShift Console Plugin. It improves user experience and policy adoption by making token rate limiting manageable through the console's visual interface.

Implementation points:

• Display attached TokenRateLimitPolicy resources in existing Gateway and HTTPRoute detail views
  • Include link-out to full resource
  • Show effective scope (e.g. default/override, matched when predicate if available)
• Add support for creating and editing a policy via a form-based interface
  • Fields should match the schema: token limit, window, predicates etc...
  • Allow user to optionally define a custom rejection response (status, body, headers)
• Show validation and error states inline (e.g., missing counter, malformed CEL predicate)
• If a route and gateway both have attached policies, clearly show which one is in effect
• Link to documentation or help text where relevant

See figma mockups https://www.figma.com/design/HnY6prXBgIn82Tlrtsg6ou/RHCL-OCP-dynamic-plugin?node-id=3249-77965&t=LdfyeIshJ2Io7SMp-0

fyi mzhong@redhat.com