Add TestRetry conformance test

[nak3]

Add TestRetry conformance test

[howardjohn]

This is going to be pretty tricky for Istio for mesh traffic if the default is not the same as Istio, since we may end up with defaulting to 2 retries, but then if a user defines an HTTPRoute we suddenly switch to no retries.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[nak3]

xref: https://gateway-api.sigs.k8s.io/geps/gep-713/

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[dprotaso]

From: kubernetes-sigs/gateway-api#184 (comment)

Retries will be controlled by a implementation (ie. istio/contour) specific policy (kubernetes-sigs/gateway-api#713) that attaches to the gateway (or whatever).

Details here: https://gateway-api.sigs.k8s.io/references/policy-attachment

Thus we won't be able to configure using the GatewayAPI - so we'll still want a test to ensure there are no retries.