K8SPSMDB-1224 Add retry mechanism for AWS CLI command in upgrade run script

[ptankov]

CHANGE DESCRIPTION

Problem:
upgrade test fails very often, because it needs to wait a little bit before listing contects of S3 bucket.

Cause:
Short explanation of the root cause of the issue if applicable.

Solution:
I added retry just like in upgrade-sharded instead of just adding a "dumb" sleep <seconds> and it should be more stable now

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?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

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 MongoDB version?
• Does the change support oldest and newest supported Kubernetes version?