Investigate a better approach to HTTPRoute rule sorting in linkerd2

What problem are you trying to solve?

While working on https://github.com/linkerd/linkerd2-proxy/pull/4604, @adleong suggested that the control plane would be a better place to perform sorting of the rules for a given HTTPRoute since the control plane has access to all the information that the HTTPRoute spec requires for enforcing precedence and breaking ties. E.g., the timestamps of when the rules were created.

How should the problem be solved?

Ideally, the control plane is updated to sort the HTTPRoute rules consumed by the dataplane based on the http route spec: https://gateway-api.sigs.k8s.io/reference/api-spec/main/spec/#httprouterule

Any alternatives you've considered?

The other alternative is to send more data to the dataplane and have it make a more intelligent decision.

Per feedback in this PR, it seems like the control plane is the preferred place for this kind of change.

How would users interact with this feature?

This isn't a new feature. The issue is investigative and can lead to linkerd2 implementing the gateway api spec correctly.

Would you like to work on this feature?

yes