K8SPG-518: Fix pitr test

[egegunes]

CHANGE DESCRIPTION

Problem: pitr test was failing sporadically.

Cause: there were two issues:

1. even though we wait for archive_timeout + 10 seconds, sometimes latest written data is not restored properly.
2. sometimes restore fails to reach specified datetime target.

Solution:

1. write more data and wait for 2 x archive_timeout + 20 seconds
2. use microsecond precision for latest restorable time.

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
one-pod	passed
operator-self-healing	passed
pitr	passed
scaling	passed
scheduled-backup	passed
self-healing	passed
start-from-backup	passed
tablespaces	passed
telemetry-transfer	passed
upgrade-consistency	passed
upgrade-minor	passed
users	passed
We run 16 out of 16

commit: https://github.com/percona/percona-postgresql-operator/pull/801/commits/1f449fafbbd8bb82547851479e981231bb7da4af image: perconalab/percona-postgresql-operator:PR-801-1f449fafb