Conformance test HTTPRouteInvalidParentRefSectionNameNotMatchingPort included in core instead of extended

[ciarams87]

What happened:
This PR introduced a new conformance test to ensure that when both Port and SectionName are specified in a HTTPRoute ParentRef, the name and port of the selected listener must match both specified values.

The issue is that this test was added to the core suite, but ParentRef.Port has extended support, not core.

What you expected to happen:
Tests for features that are extended support should be part of the extended test suite.

How to reproduce it (as minimally and precisely as possible):
Run the conformance test suite against an implementation without ParentRef.Port support. See https://github.com/nginxinc/nginx-gateway-fabric/actions/runs/7041855950/job/19165071974 for an example.

Anything else we need to know?:

[ciarams87]

I opened an issue for tracking purposes, but I'm happy to work on the fix for this myself 😁
/assign

[shaneutt]

@mlavacca created #2623 before this issue was reported: just heads up you two might be working on the same thing!

[mlavacca]

Yep, this issue will be fixed by #2623. Thanks @shaneutt for being so vigilant 😄

[ciarams87]

Oh, I missed this PR - thanks @shaneutt and @mlavacca !

[shaneutt]

Yep, sorry for the confusion just a bit of bad timing!

/assign @mlavacca

Thank you so much for taking the time here. If you are looking for more opportunities to contribute to Gateway API and need some support in that, let us know! We're very happy to try and provide that support and we're very active on #sig-network-gateway-api in Kubernetes Slack!