feature(translator): cluster and endpoint xds metadata

[guydc]

What type of PR is this?

What this PR does / why we need it:
Creates XDS filter metadata for cluster and endpoint resources, based on xRoute and Service/ServiceImport/Backend appropriately.

Which issue(s) this PR fixes:

Fixes #5523

Release Notes: Yes

[codecov]

Codecov Report

Attention: Patch coverage is 97.61905% with 1 line in your changes missing coverage. Please review.

Project coverage is 70.52%. Comparing base (eb7266c) to head (915b4cb).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/xds/translator/translator.go	88.88%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5875      +/-   ##
==========================================
+ Coverage   70.48%   70.52%   +0.04%     
==========================================
  Files         219      219              
  Lines       36318    36347      +29     
==========================================
+ Hits        25597    25634      +37     
+ Misses       9197     9192       -5     
+ Partials     1524     1521       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[arkodg]

thanks @guydc, seeing a lot of test cases being updated :) , requesting one more which set the name of a route rule, if this already exists, please ignore

[guydc]

thanks @guydc, seeing a lot of test cases being updated :) , requesting one more which set the name of a route rule, if this already exists, please ignore

Should be covered by httproute-with-metadata.in.yaml, also added to egctl test default-resources.all.yaml demonstrating end-to-end of name from gw-api to xds.

[mathetake]

looking good... thank you!

[arkodg]

LGTM thanks !

there's one edge case that needs to be solved, can be a follow up.

For some cases, specifically when a Backend Filter exists, we create a

• Weighted xDS cluster for every route rule
• xDS cluster for every backendRef

lets track this with a GH issue

[mathetake]

envoyproxy/envoy#39604

With this upstream change, this locality endpoints level metadata can be utilized as part of attribute, notably the extproc should be able to access that