chore: improve xRoute status errors

[zhaohuabing]

#5747 improves the route status for HTTPRoute. This PR does the same for other(GRPC/TLS/TCP/UDP) Routes.

• Translation errors of all the RouteRule are now surfaced to the XRoute status. This makes it easier for users to find out which parts of their config are invalid.
• Consolidate all the Route translation error handling in a single location rather than updating status throughout the code. This simplifies the XRoute translation logic and allows us to aggregate all errors into a single status message for better clarity.
• Fix some inconsistent behavior between HTTPRoute and other Route types.

[codecov]

Codecov Report

Attention: Patch coverage is 84.93151% with 22 lines in your changes missing coverage. Please review.

Project coverage is 65.25%. Comparing base (7c88e66) to head (9953a63).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/gatewayapi/route.go	83.45%	19 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5803      +/-   ##
==========================================
- Coverage   65.32%   65.25%   -0.07%     
==========================================
  Files         222      222              
  Lines       35459    35418      -41     
==========================================
- Hits        23164    23113      -51     
- Misses      10859    10867       +8     
- Partials     1436     1438       +2     

☔ 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.

[zhaohuabing]

There is an inconsistency between the current Accepted status behavior of TCPRoute and HTTPRoute when the envoyproxy tls setting is invalid. To align with the HTTPRoute, the Accepted status for TCPRoute should be set to True here.

https://github.com/envoyproxy/gateway/blob/81e41c13520362f7b47b9c5e59af1b5bca279f14/internal/gatewayapi/testdata/envoyproxy-tls-settings-invalid-ns.out.yaml#L124-L136

[zhaohuabing]

Same here: https://github.com/envoyproxy/gateway/pull/5803/files#r2057720214

[zhaohuabing]

Same here: https://github.com/envoyproxy/gateway/pull/5803/files#r2057720214

[zhaohuabing]

The condition for multiple rules should be Accepted instead of ResolvedRefs.

[zhaohuabing]

The condition for multiple rules should be Accepted instead of ResolvedRefs.

[zhaohuabing]

The Appcepted status should be True when failed to Resolve the BackendRef for a MirrorFiliter.

[arkodg]

what about the case when backend has no endpoints, do we end up here ?

[zhaohuabing]

Yes, the pervious behavior for backend without endpoints is 500 direct response, and no error status for Accepted and Resolved conditions. This PR doesn't change it.