[E2E] Fix failing tests because of change in cluster names

[Ankitasw]

What type of PR is this?
/kind failing-test

What this PR does / why we need it:
There is an issue caused by PR which increases the cluster name in below tests:

• Ignition tests which requires s3 bucket name to be within 63 characters limit.
• External infrastructure tests where spec name is coming up as empty which violates RFC 1123 while creating cluster.

This PR keeps the naming of clusters within range such that it satisfies all validations in above tests.

Checklist:

• squashed commits
• includes documentation
• adds unit tests
• adds or updates e2e tests

[k8s-ci-robot]

@Ankitasw: This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Ankitasw]

/test pull-cluster-api-provider-aws-e2e

[Ankitasw]

/test pull-cluster-api-provider-aws-e2e

[sedefsavas]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sedefsavas

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sedefsavas]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment