K8SPG-648 Fix patroni-version-check

[pooknull]

DESCRIPTION

Problem:
The operator triggers the patroni-version-check only when the .spec.postgresVersion field is updated. However, if the user updates the images without modifying this field, the version check is not triggered, leading to an incorrect patroni version in the .status. This also results in a persistent error: get latest commit timestamp: primary pod not found.

Solution:
Start the patroni-version-check pod after all instance pods have been updated with the new image. The operator will determine this by comparing the new .status.postgres.imageID field with the image IDs of the instance pods.

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

commit: 9ab5634
image: perconalab/percona-postgresql-operator:PR-1071-9ab563432