Support for Backend priorities beyond active/passive levels

[yuzisun]

Description:
Currently, Envoy Gateway supports two levels of backend priorities: active and passive. While this is sufficient for basic use cases, it limits more advanced traffic management scenarios for GenAI traffic where multiple levels of backend priorities are required for multiple regions, model providers, on-demand and provisioned throughput with different context length.

For multi-region deployment, we want to prioritize backends in following orders to achieve higher SLO target.

• us-east-1
• us-east-2
• us-west-2

For on-demand, provisioned throughput deployment, we want to prioritize backends in following orders based on the capacity.

• PT with small context length
• PT with large context length
• on-demand endpoint

Extend the envoy gateway configuration to support multiple backend priority levels which can be achieved by introducing the priority field in the backend configuration, allowing users to specify a numerical priority level.

[optional Relevant Links:]
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/priority
envoyproxy/ai-gateway#34

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

[arkodg]

this can be solved with a priority field in the Backend resource, probably needs a CEL validation to make sure fallback and priority are not set at the same time