Gateway API: unsupported filters should be reflected in route status

[kenjenkins]

If a route contains a filter with a type that is not supported, this should be reflected in the "Accepted" status condition:

Unknown values here must result in the implementation setting the Accepted Condition for the Route to status: False, with a Reason of UnsupportedValue.

(reference)