kops: Tagging Instance Profile isn't supported in all AWS Regions and blocks cluster update to 1.21

/kind bug

1. What kops version are you running? The command kops version, will display this information.

1.21.0

2. What Kubernetes version are you running? kubectl version will print the version if a cluster is running or provide the Kubernetes version specified as a kops flag.

1.21.4

3. What cloud provider are you using?

AWS (Isolated Region)

4. What commands did you run? What is the simplest way to reproduce this issue?

Trying to update a cluster from 1.20 to 1.21 fails (it was successful in 1.20) as 1.21 attempts to tag the instance profiles, and this feature is not support yet in this AWS region whose capabilities lag those of commercially available regions.

5. What happened after the commands executed?

invalid / operation not permitted, cluster update is blocked and cannot complete.

6. What did you expect to happen?

Successful cluster update.

7. Please provide your cluster manifest. Execute kops get --name my.example.com -o yaml to display your cluster manifest. You may want to remove your cluster name and other sensitive information.

(nothing special here - same yaml as is working in 1.20 - just 1.21 is tagging where it didnt used to tag.

8. Please run the commands with most verbose logging by adding the -v 10 flag. Paste the logs into this report, or in a gist and provide the gist link here.

9. Anything else do we need to know?