K8SPG-844: Don't modify archive_command if trackLatestRestorableTime is disabled

[egegunes]

CHANGE DESCRIPTION

Even if trackLatestRestorableTime is disabled, operator modifies archive_command. Since it's possible to have performance degradation because of the modified archive_command, we need to ensure operator doesn't do anything with archive_command if trackLatestRestorableTime is disabled.

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	Result	Time
backup-enable-disable	passed	00:10:41
custom-extensions	passed	00:14:10
custom-tls	passed	00:05:49
database-init-sql	passed	00:03:31
demand-backup	passed	00:27:08
finalizers	passed	00:03:48
init-deploy	passed	00:02:42
monitoring	passed	00:08:36
monitoring-pmm3	passed	00:09:10
one-pod	passed	00:05:47
operator-self-healing	passed	00:08:12
pgvector-extension	passed	00:03:21
pitr	passed	00:11:34
scaling	passed	00:05:55
scheduled-backup	passed	00:27:19
self-healing	passed	00:09:18
sidecars	passed	00:02:26
start-from-backup	passed	00:10:52
tablespaces	passed	00:06:31
telemetry-transfer	passed	00:03:19
upgrade-consistency	passed	00:08:10
upgrade-minor	failure	00:03:25
users	passed	00:04:31
We run 23 out of 23		03:16:26

commit: a47b15c
image: perconalab/percona-postgresql-operator:PR-1290-a47b15cce