K8SPG-719 use image.tag and image.repository to configure pmm3 server on e2e tests

[gkech]

CHANGE DESCRIPTION

Problem:
With the image and tag misconfigured, they are ignored, and instead, we are always using by default the latest released version.

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

Solution:
based on this: https://github.com/percona/percona-helm-charts/tree/main/charts/pmm#percona-monitoring-and-management-pmm-parameters

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	Status
backup-enable-disable	failure
custom-extensions	failure
custom-tls	failure
demand-backup	failure
finalizers	skipped
init-deploy	skipped
monitoring	skipped
monitoring-pmm3	skipped
one-pod	skipped
operator-self-healing	skipped
pitr	skipped
scaling	skipped
scheduled-backup	skipped
self-healing	skipped
sidecars	skipped
start-from-backup	skipped
tablespaces	skipped
telemetry-transfer	skipped
upgrade-consistency	skipped
upgrade-minor	skipped
users	skipped
We run 4 out of 21

commit: d9716bf
image: perconalab/percona-postgresql-operator:PR-1144-d9716bf4f