conformance: set NotAllowedByListeners in HTTPRoute status

[mlavacca]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

When the HTTPRoute references a listener in a different namespace, and there is an invalid ReferenceGrant that allows it, we need to set the NotAllowedByListeners reason in the Accepted condition.

More details: kubernetes-sigs/gateway-api#1714

Proposed Solution

No response

Additional information

No response

Acceptance Criteria

• the conformance test HTTPRouteInvalidCrossNamespaceParentRef is passing after having bumped the Gateway API to 0.6.2 (still unreleased at the moment of writing)

[rainest]

This was apparently already passing after some point? I did nothing other than update to 0.7.1 and it passed (other tests failed): b3964c2

2023-06-06T21:34:00.6679796Z     --- PASS: TestGatewayConformance/HTTPRouteInvalidCrossNamespaceParentRef (1.05s)
2023-06-06T21:34:00.6680909Z         --- PASS: TestGatewayConformance/HTTPRouteInvalidCrossNamespaceParentRef/HTTPRoute_should_have_an_Accepted:_false_condition_with_reason_NotAllowedByListeners (0.01s)
2023-06-06T21:34:00.6681932Z         --- PASS: TestGatewayConformance/HTTPRouteInvalidCrossNamespaceParentRef/Route_should_not_have_Parents_set_in_status (0.00s)
2023-06-06T21:34:00.6683026Z         --- PASS: TestGatewayConformance/HTTPRouteInvalidCrossNamespaceParentRef/Gateway_should_have_0_Routes_attached (1.01s)

That was without the code to explicitly check it (1507095). Not sure when or what would have changed it earlier since it looks like most of the code to set the not allowed status was added before this was filed originally.