K8SPG-583: Set correct operator version for version meta

[inelpandzic]

CHANGE DESCRIPTION

Problem: When setting version.Meta we set the hardcoded v2.Version operator version. We need to set cr.Spec.CRVersion.

CHECKLIST

Jira

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

Tests

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

Config/Logging/Testability

• [x] Are all needed new/changed options added to default YAML files?
• [x] Are the manifests (crd/bundle) regenerated if needed?
• [x] Did we add proper logging messages for operator actions?
• [x] Did we ensure compatibility with the previous version or cluster upgrade process?
• [x] Does the change support oldest and newest supported PG version?
• [x] Does the change support oldest and newest supported Kubernetes version?

[JNKPercona]

Test name	Status
custom-extensions	passed
demand-backup	passed
init-deploy	passed
monitoring	passed
operator-self-healing	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-minor	passed
users	passed
We run 13 out of 13

commit: https://github.com/percona/percona-postgresql-operator/pull/773/commits/6dc27dd2976a3b823f911b83cb1a0d82132c95f3 image: perconalab/percona-postgresql-operator:PR-773-6dc27dd29