K8SPXC-1668: proxysql3 support

[pooknull]

https://perconadev.atlassian.net/browse/K8SPXC-1668

DESCRIPTION

This PR updates the default IMAGE_PROXY to percona/proxysql3:3.0 and applies minor test fixes to verify that the operator supports proxysql v3

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?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

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 PXC version?
• Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test Name	Result	Time
auto-tuning-8-0	passed	00:19:27
allocator-8-0	passed	00:13:03
backup-storage-tls-8-0	passed	00:22:28
cross-site-8-0	passed	00:34:44
custom-users-8-0	passed	00:12:58
demand-backup-cloud-8-0	passed	00:56:02
demand-backup-encrypted-with-tls-8-0	passed	00:43:52
demand-backup-8-0	passed	00:41:34
demand-backup-flow-control-8-0	passed	00:11:17
demand-backup-parallel-8-0	passed	00:08:57
demand-backup-without-passwords-8-0	passed	00:16:52
haproxy-5-7	passed	00:14:02
haproxy-8-0	passed	00:14:38
init-deploy-5-7	passed	00:16:24
init-deploy-8-0	passed	00:16:41
limits-8-0	passed	00:12:12
monitoring-2-0-8-0	passed	00:22:46
monitoring-pmm3-8-0	passed	00:18:08
one-pod-5-7	passed	00:16:58
one-pod-8-0	passed	00:14:07
pitr-8-0	passed	00:43:05
pitr-gap-errors-8-0	passed	00:56:50
proxy-protocol-8-0	passed	00:09:32
proxy-switch-8-0	failure	01:30:05
proxysql-sidecar-res-limits-8-0	passed	00:08:50
proxysql-scheduler-8-0	passed	00:16:22
pvc-resize-5-7	passed	00:15:06
pvc-resize-8-0	passed	00:17:01
recreate-8-0	passed	00:17:17
restore-to-encrypted-cluster-8-0	passed	00:25:27
scaling-proxysql-8-0	passed	00:08:29
scaling-8-0	passed	00:10:54
scheduled-backup-5-7	passed	01:04:47
scheduled-backup-8-0	passed	01:02:45
security-context-8-0	passed	00:25:47
smart-update1-8-0	passed	00:32:10
smart-update2-8-0	passed	00:38:22
storage-8-0	passed	00:10:41
tls-issue-cert-manager-ref-8-0	passed	00:08:45
tls-issue-cert-manager-8-0	passed	00:10:06
tls-issue-self-8-0	passed	00:13:22
upgrade-consistency-8-0	passed	00:10:56
upgrade-haproxy-5-7	passed	00:25:01
upgrade-haproxy-8-0	passed	00:24:47
upgrade-proxysql-5-7	passed	00:20:29
upgrade-proxysql-8-0	passed	00:19:08
users-5-7	failure	00:09:35
users-8-0	passed	00:24:59
validation-hook-8-0	passed	00:01:57

Summary	Value
Tests Run	49/49
Job Duration	04:06:44
Total Test Time	19:10:11

commit: 4bd70d7
image: perconalab/percona-xtradb-cluster-operator:PR-2265-4bd70d71

[eleo007]

But why with proxysql 3 all the nodes are now added to writer group? It should contain only pxc pod 0

[hors]

@egegunes ^