fix: use UnsupportedValue as the reason for unresolved filters

[zhaohuabing]

fix: #7603

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.45%. Comparing base (986c609) to head (80568ba).
⚠️ Report is 547 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7642      +/-   ##
==========================================
+ Coverage   72.41%   72.45%   +0.03%     
==========================================
  Files         232      232              
  Lines       34278    34278              
==========================================
+ Hits        24824    24835      +11     
+ Misses       7679     7669      -10     
+ Partials     1775     1774       -1     

☔ 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kkk777-7]

LGTM!

[kkk777-7]

non-bloking:

should we update function comment too?
InvalidKind -> UnsupportedValue

// Unresolvable or unsupported filters should be treated like other reference failures:
// (`Accepted` will be set to true, `ResolvedRefs` to false with a `InvalidKind` Reason,
// and traffic that would have matched the filter should receive a 500 error.)
// ref: https://gateway-api.sigs.k8s.io/geps/gep-1364/#new-and-updated-conditions
func (t *Translator) processUnresolvedHTTPFilter(errMsg string, filterContext *HTTPFiltersContext) status.Error {

[zhaohuabing]

InvalidKind

InvalidKind is just an example in the GEP, and it's not the only reason. I removed it from the comments.

[kkk777-7]

InvalidKind is just an example in the GEP, and it's not the only reason. I removed it from the comments.

Got it. thanks!