fix: ensure s3 url has no bucket for velero in AWS

Description

Fix the Velero backup bucket s3 URL for AWS.

Supporting information

The error we are fixing:

An error occurred: Get "https://velero-backup-keithg-20230607081530686500000001.velero-backup-keithg-20230607081530686500000001.s3.amazonaws.com/backups/velero-hourly-backup-20230607130051/velero-hourly-backup-20230607130051-logs.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAWZH65HNIVJYPU6UY%2F20230607%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230607T144907Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=51d5f6da6d90d4d7be5ae1eb5b50223fec1c06520c13340adc3af256c56335da": x509: certificate is valid for *.s3.amazonaws.com, s3.amazonaws.com, not velero-backup-keithg-20230607081530686500000001.velero-backup-keithg-20230607081530686500000001.s3.amazonaws.com

Testing instructions

Steps to test the changes:

1. Apply changes
2. Create a new backup

Dependencies

N/A

Screenshots

N/A

Checklist

If any of the items below is not applicable, do not remove them, but put a check in it.

• All providers include the new feature/change
• All affected providers can provision new clusters
• Unit tests are added/updated
• Documentation is added/updated
• The TOOLS_CONTAINER_IMAGE_VERSION in ci_vars.yml is updated
• The grove-template repository is updated

Additional context

N/A