Add NetworkPolicyStatus to ineligible_endpoints.yaml

[riaankleinhans]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Add NetworkPolicyStatus endpoints to ineligible_endpoint.yaml as the endpoints are currently future gated and will only recieve e2e & confromance tests in 1.25. This would prevent the endpoints for incorrectly showing up as new conformance technical debt.

• readNetworkingV1NamespacedNetworkPolicyStatus
• patchNetworkingV1NamespacedNetworkPolicyStatus
• replaceNetworkingV1NamespacedNetworkPolicyStatus`

Implementation on Network Policy Status #107963

Special notes for your reviewer:
As of 1.22 APISnoop Ineligible endpoints are pulled from the community owned inelegible_endpoint.yaml file

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

[riaankleinhans]

/triage accepted
/assign @johnbelamaric @rikatz

Should be in milestone 1.24

[riaankleinhans]

/cc @hh

[rikatz]

/lgtm
Tks

[riaankleinhans]

/test pull-kubernetes-e2e-gce-ubuntu-containerd

Unrelated flake

I0404 20:15:29.353]   test/e2e/autoscaling/dns_autoscaling.go:169
I0404 20:15:29.353] STEP: Replace the dns autoscaling parameters with testing parameters
I0404 20:15:29.353] Apr  4 20:14:51.340: INFO: DNS autoscaling ConfigMap updated.
I0404 20:15:29.353] STEP: Wait for kube-dns scaled to expected number
I0404 20:15:29.353] Apr  4 20:14:51.340: INFO: Waiting up to 5m0s for kube-dns to reach expected replicas
I0404 20:15:29.354] Apr  4 20:14:53.463: INFO: Replicas not as expected: got 2, expected 3
I0404 20:15:29.354] Apr  4 20:14:55.465: INFO: Replicas not as expected: got 2, expected 3
I0404 20:15:29.354] Apr  4 20:14:57.463: INFO: Replicas not as expected: got 2, expected 3
I0404 20:15:29.354] Apr  4 20:14:59.468: INFO: Replicas not as expected: got 2, expected 3

[dims]

/approve
/lgtm

(will still need testdata approver as i don't have privileges here)

[johnbelamaric]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, johnbelamaric, Riaankl

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 [johnbelamaric]

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

[dims]

/milestone v1.24