Add tested x86_64 instance types for AWS Local Zone

[yunjiang29]

AWS Local Zone is supported starting from 4.12 OCPPLAN-9630, adding tested instance types list for AWS Local Zone according to discussion in documentation PR 54535.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mtulio for approval by writing /assign @mtulio in a comment. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• docs/user/aws/OWNERS

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

[yunjiang29]

@patrickdillon can you help review this PR? thanks

[openshift-ci]

@yunjiang29: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-shared-vpc	e34e12d	link	false	/test e2e-aws-ovn-shared-vpc
ci/prow/okd-scos-images	e34e12d	link	true	/test okd-scos-images
ci/prow/e2e-aws-ovn-single-node	e34e12d	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-proxy	e34e12d	link	false	/test e2e-aws-ovn-proxy
ci/prow/e2e-aws-ovn-fips	e34e12d	link	false	/test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-disruptive	e34e12d	link	false	/test e2e-aws-ovn-disruptive
ci/prow/e2e-aws-ovn-imdsv2	e34e12d	link	false	/test e2e-aws-ovn-imdsv2
ci/prow/e2e-aws-ovn-upgrade	e34e12d	link	false	/test e2e-aws-ovn-upgrade

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[mtulio]

/lgtm

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.