K8SPG-651: wait longer for migration-backup-s3-pgbackrest-restore

[eleo007]

CHANGE DESCRIPTION

Problem:
migration-backup-s3 test fails on step 09 because it takes more than 5 sec for migration-backup-s3-pgbackrest-restore job to be created. As a result when we run kubectl -n $NAMESPACE wait --for=condition=Complete there is no object and test fails.

Solution:
Wait for longer time before checking restore job completion,

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?