K8SPS-358 add MySQL 8.3 and MySQL 8.4 support

[hors]

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

[JNKPercona]

Test name	Status
version-service	failure
async-ignore-annotations	failure
auto-config	failure
config	failure
config-router	failure
demand-backup	failure
gr-demand-backup	failure
gr-demand-backup-haproxy	failure
gr-finalizer	failure
gr-haproxy	failure
gr-ignore-annotations	failure
gr-init-deploy	failure
gr-one-pod	failure
gr-recreate	failure
gr-scaling	failure
gr-scheduled-backup	failure
gr-security-context	failure
gr-self-healing	failure
gr-tls-cert-manager	failure
gr-users	failure
haproxy	failure
init-deploy	failure
limits	passed
monitoring	failure
one-pod	failure
operator-self-healing	failure
recreate	failure
scaling	failure
scheduled-backup	failure
service-per-pod	failure
sidecars	failure
smart-update	failure
tls-cert-manager	failure
users	failure
We run 34 out of 34

commit: https://github.com/percona/percona-server-mysql-operator/pull/676/commits/5e3c84d9c3b702f5e697a1132399866045a8e5ac image: perconalab/percona-server-mysql-operator:PR-676-5e3c84d9