gRPCRoute tranlator cannot handle wildcard rule

[rainest]

Prior to kubernetes-sigs/gateway-api#1753, the gRPC spec provided a default method match if no matches were specified. This broke the intended meaning of a no-match rule, which should match all requests.

The gRPC route translator loops over matches to generate routes associated with a GRPCRoute resource. If a rule has no matches, it will result in 0 associated routes. I did not review the ATC generator behavior.

The current example test manifest uses a 0-match rule. After upgrading the Gateway APIs CRDs to 0.7.1, API requests no longer populated default matches for it. This results in the translator generating 0 routes, whereas it should instead generate a single route that matches any request for example.com

To fix:

• When GWAPI 0.7.1 is installed, a 0-match gRPC rule must generate a single Kong route that matches all requests that match the GRPCRoute hostname with the traditional router.
• The same is true with the expression router.