proxy api: support destination ip/port matching

[stevenctl]

Description

Allow filter chain matches to match on destination IP/port.

This bug fixes ... \ This new feature can be used to ...

API changes

In Matcher added:

• uint32 destination_port
• CidrRange[] prefix_ranges

(continuing to duplicate what envoy has)

Code changes

Implement the translation from Proxy to Envoy xDS for the new fields.
This was only done in the same places that SourcePrefixRanges were already uses.

Context

Related to #9471

Interesting decisions

We chose to do things this way because ...

Testing steps

I manually verified behavior by relying on it in an experimental fork.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[github-actions]

Visit the preview URL for this PR (updated for commit 2c0ba48):

https://gloo-edge--pr9485-stevenctl-proxy-matc-1bxrsouj.web.app

_{(expires Fri, 07 Jun 2024 17:02:44 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 77c2b86e287749579b7ff9cadb81e099042ef677}

[sam-heilbron]

Changes LGTM! Could we add some basic unit tests to demonstrate the new matching capabilities and perhaps an e2e test as well to show that the traffic is routed appropriately? https://github.com/solo-io/gloo/blob/main/test/e2e/hybrid_test.go#L172 Might be a good set of tests to build off of

[stevenctl]

@sam-heilbron should be good to go