K8SPG-510 update cluster status

[nmarukovich]

CHANGE DESCRIPTION

Problem: Short explanation of the problem. The problem was that we jumped from ready to paused without stopping step. now it should work correctly. 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?
• [ ] Are the manifests (crd/bundle) regenerated if needed?
• [ ] 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
demand-backup	passed
init-deploy	passed
monitoring	passed
operator-self-healing	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
start-from-backup	passed
telemetry-transfer	passed
upgrade-minor	passed
users	passed
We run 12 out of 12

commit: https://github.com/percona/percona-postgresql-operator/pull/743/commits/4d381ad328798487b83dc4bd62e1f0c2ab978356 image: perconalab/percona-postgresql-operator:PR-743-4d381ad32