Update AMI filter for rocky linux

[ahmedwaleedmalik]

What this PR does / why we need it:
*Rocky-8-EC2-8*.x86_64 doesn't work anymore and we need to drop -8* https://github.com/kubermatic/kubeone/blob/main/examples/terraform/aws/variables.tf#L220

Which issue(s) this PR fixes:

Fixes #

What type of PR is this?

/kind chore

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

[kubermatic-bot]

LGTM label has been added.

Git tree hash: 3a83a9ef149c07b27a44001e97571af2419e7098

[ahmedwaleedmalik]

/approve

[kubermatic-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahmedwaleedmalik

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 [ahmedwaleedmalik]

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

[xrstf]

/cherrypick release/v1.57

[xrstf]

/cherrypick release/v1.58

[xrstf]

/cherrypick release/v1.59

[kubermatic-bot]

@xrstf: #1803 failed to apply on top of branch "release/v1.57":

Applying: Update AMI filter for rocky linux
Using index info to reconstruct a base tree...
M	pkg/cloudprovider/provider/aws/provider.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/cloudprovider/provider/aws/provider.go
CONFLICT (content): Merge conflict in pkg/cloudprovider/provider/aws/provider.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update AMI filter for rocky linux
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release/v1.57

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.

[kubermatic-bot]

@xrstf: #1803 failed to apply on top of branch "release/v1.58":

Applying: Update AMI filter for rocky linux
Using index info to reconstruct a base tree...
M	pkg/cloudprovider/provider/aws/provider.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/cloudprovider/provider/aws/provider.go
CONFLICT (content): Merge conflict in pkg/cloudprovider/provider/aws/provider.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update AMI filter for rocky linux
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release/v1.58

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.

[kubermatic-bot]

@xrstf: #1803 failed to apply on top of branch "release/v1.59":

Applying: Update AMI filter for rocky linux
Using index info to reconstruct a base tree...
M	pkg/cloudprovider/provider/aws/provider.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/cloudprovider/provider/aws/provider.go
CONFLICT (content): Merge conflict in pkg/cloudprovider/provider/aws/provider.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update AMI filter for rocky linux
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release/v1.59

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.