K8SPG-782 assign patroni version to status when patroni label is configured through the cr option

[gkech]

CHANGE DESCRIPTION

Problem:

When we configure

metadata:
  name: cluster1
  annotations:
    pgv2.percona.com/custom-patroni-version: "4"

We get the following error:

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

Solution:

After the fix, using this image: perconalab/percona-postgresql-operator:K8SPG-782-3

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?

[gkech]

upgrade-consistency fails with the following:

     	postgrescluster-controller	
logger.go:42: 14:52:34 | upgrade-consistency | 2025-06-09 14:48:54 +0000 UTC	Warning	PostgresCluster.postgres-operator.crunchydata.com upgrade-consistency		UnableToCreateStanzas	(combined from similar events): command terminated with exit code 39: repo1-path = /pgbackrest/repo1
    2025-06-09 14:52:00.145 P00  ERROR: [039]: expected value '2.55.0' for greeting key 'version' but got '2.54.2'
                                        HINT: is the same version of pgBackRest installed on the local and remote host?
    2025-06-09 14:52:00.245 P00  ERROR: [039]: expected value '2.55.0' for greeting key 'version' but got '2.54.2'
                                        HINT: is the same version of pgBackRest installed on the local and remote host?

[JNKPercona]

Test name	Status
backup-enable-disable	passed
custom-extensions	passed
custom-tls	passed
demand-backup	passed
finalizers	passed
init-deploy	passed
monitoring	passed
monitoring-pmm3	passed
one-pod	passed
operator-self-healing	passed
pitr	passed
scaling	passed
scheduled-backup	passed
self-healing	failure
sidecars	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-consistency	passed
upgrade-minor	passed
users	passed
We run 21 out of 21

commit: 9f68047
image: perconalab/percona-postgresql-operator:PR-1165-9f6804715