### Promotion request for port forwarding e2e tests

As part of addressing the [remaining untested endpoints](https://apisnoop.cncf.io/conformance-progress/endpoints/1.26.0/?filter=untested) for Conformance the api endpoint [connectCoreV1GetNamespacedPodPortforward](https://apisnoop.cncf.io/1.24.0/stable/core/connectCoreV1GetNamespacedPodPortforward?conformance-only=true) is tested by the following two e2e tests which haven't been promoted to conformance.

- [Port forwarding With a server listening on 0.0.0.0 should support forwarding over websockets](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/kubectl/portforward.go#L470)
- [Port forwarding With a server listening on localhost should support forwarding over websockets](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/kubectl/portforward.go#L492)

Both tests are using a common function [doTestOverWebSockets](https://github.com/kubernetes/kubernetes/blob/d57b6128eb6c3d3677ba5d8828fd3756989da133/test/e2e/kubectl/portforward.go#L362) which looks to meet the requirements for both tests to be [promoted to conformance](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md#conformance-test-requirements).

Also, the following links show the current Testgrid status for each test.

- [Port forwarding With a server listening on 0.0.0.0 should support forwarding over websockets](https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-default&width=5&graph-metrics=test-duration-minutes&include-filter-by-regex=localhost.should.support.forwarding.over.websockets)
- [Port forwarding With a server listening on localhost should support forwarding over websockets](https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-default&width=5&graph-metrics=test-duration-minutes&include-filter-by-regex=localhost.should.support.forwarding.over.websockets)

Is there any reason that SIG-CLI can see why these tests can't be promoted to conformance?