fix: Correct Karpenter EC2 service principal DNS suffix in non-commercial regions

[bryantbiggs]

Description

• Correct Karpenter EC2 service principal DNS suffix in non-commercial regions

Motivation and Context

• Resolves Karpenter role doesn't work in China #3155

Breaking Changes

• No

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[antonbabenko]

This PR is included in version 20.24.1 🎉

[raonitimo]

Maybe having both names would be better. Found this in AWS doc:

Service principals in policies – In IAM policies where the principal is a service, the service principal name can include the following formats, with "service" replaced by the name of the service:

service.amazonaws.com

service.amazonaws.com.cn

Do not try to guess the service principal, because it is case sensitive and the format can vary across Amazon services. The service principal is defined by the service. To learn the service principal for a service, see the documentation for that service. For some services, see [Amazon services that work with IAM](https://docs.amazonaws.cn/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) and look for the services that have Yes in the Service-linked role column. Choose a Yes with a link to view the service-linked role documentation for that service. View the Service-linked role permissions section for that service to view the service principal.

[bryantbiggs]

Why is that better?

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.