Add GRPCRoute coverage in request-mirror tests

[LiorLieberman]

What would you like to be added:
GRPCRoute coverage in http-request-mirror tests

Why this is needed:
cause.. why not? :)

This is to improve coverage for GRPCRoute conformance tests.

We should probably associate this with a different supportedFeature to allow gradual/selective support. Thoughts?

/cc @mikemorris @kflynn @robscott

[mikemorris]

I think it would be a new group, i.e. grpc-request-mirror, but we could factor out any common logic and yea we should do this, probably just a matter of prioritization/contribution and review bandwidth.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten