K8SPG-866 use discovery.k8s.io/v1 EndpointSlice

[gkech]

CHANGE DESCRIPTION

Problem:
Short explanation of the problem.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
Short explanation of the solution we are providing with this PR.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Are all needed new/changed options added to the Helm Chart?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported PG version?
• Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test Name	Result	Time
backup-enable-disable	passed	00:00:00
custom-extensions	failure	00:04:54
custom-tls	failure	00:05:01
database-init-sql	failure	00:02:12
demand-backup	failure	00:05:42
finalizers	passed	00:00:00
init-deploy	failure	00:02:33
monitoring	passed	00:00:00
monitoring-pmm3	passed	00:00:00
one-pod	failure	00:02:33
operator-self-healing	failure	00:03:46
pgvector-extension	failure	00:02:20
pitr	failure	00:02:44
scaling	failure	00:02:32
scheduled-backup	failure	00:06:54
self-healing	failure	00:03:51
sidecars	passed	00:00:00
start-from-backup	failure	00:04:52
tablespaces	failure	00:02:46
telemetry-transfer	passed	00:00:00
upgrade-consistency	passed	00:00:00
upgrade-minor	passed	00:00:00
users	failure	00:02:35
We run 23 out of 23		00:55:21

commit: 549a05a
image: perconalab/percona-postgresql-operator:PR-1307-549a05a5d