Update ineligible endpoints yaml to include debug endpoints

[heyste]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
The general view is that the following endpoints are for debug purposes only and shouldn't be part of conformance.
This PR would prevent these endpoints been show as conformance technical debt.

• connectCoreV1GetNamespacedPodAttach
• connectCoreV1GetNamespacedPodPortforward
• connectCoreV1PostNamespacedPodAttach

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

Release note:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

/sig architecture
/area conformance
/sig node

[dims]

/release-note-none
/assign @liggitt

[heyste]

/test pull-kubernetes-e2e-gce
flake: [sig-storage] In-tree Volumes [Driver: hostPathSymlink] [Testpattern: Inline-volume (default fs)] subPath should support existing directory

{ failed [FAILED] while waiting for hostPath init pod to succeed: Timed out after 300.037s.

[heyste]

/test pull-kubernetes-conformance-image-test
Flake:

W0213 20:44:00.869] subprocess.CalledProcessError: Command '('bash', '-c', 'cd ./../../k8s.io/kubernetes && source ./../test-infra/experiment/kind-conformance-image-e2e.sh')' returned non-zero exit status 1.
E0213 20:44:00.869] Command failed
I0213 20:44:00.869] process 647 exited with code 1 after 23.4m
E0213 20:44:00.870] FAIL: pull-kubernetes-conformance-image-test 

[heyste]

/test pull-kubernetes-conformance-image-test

[Riaankl]

/triage accepted
/priority important-soon

[dims]

consensus on slack:
https://kubernetes.slack.com/archives/C78F00H99/p1676398815869339

/approve

[smarterclayton]

/lgtm

If we do find a situation where the conformance status of these endpoints is important, we will revisit within the conformance wg and use it as a test case for understanding what the bounds of conformance for workloads are.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 8d0839b4d03b36a2337694cd909656fc60cbb680

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, heyste

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/conformance/testdata/OWNERS [dims]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment