[EKS] [announcement]: Temporary rollback of enforcing upgrade insights on update cluster version

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Which service(s) is this announcement for?**
EKS

**What are you announcing?**
Yesterday we launched a new [feature](https://aws.amazon.com/about-aws/whats-new/2025/03/amazon-eks-enforces-upgrade-insights-check-cluster-upgrades/) in EKS where we now check and enforce the status of [EKS upgrade insights](https://docs.aws.amazon.com/eks/latest/userguide/cluster-insights.html) as part the [UpdateClusterVersion](https://docs.aws.amazon.com/eks/latest/APIReference/API_UpdateClusterVersion.html) API.

This feature is intended to prevent customers from accidentally upgrading when EKS has identified issues that have strong chance causing impact on upgrade. If you are encountering this new behavior when upgrading, the best course of action is to check EKS upgrade insights for the findings marked as ERROR. EKS upgrade insights refreshes on a 24 hour basis, and successful remediation will result in PASSING status after the next refresh (except in the case of deprecated API checks, see #2569). Then you can upgrade without needing the force flag.

While we launched with support in AWS owned tools like [aws cli](https://docs.aws.amazon.com/cli/latest/reference/eks/update-cluster-version.html) and [CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-eks-cluster.html#cfn-eks-cluster-force), we recognize many EKS customers use 3rd party management tools (such as Terraform) which have not yet been updated, and these users cannot easily pass the force flag.

Given this, we have decided to temporarily rollback this feature (the --force flag will still exist, but be treated as a no-op) and give time for community tools to catch up releasing support for the new force flag. We are aiming to have this change completed by end day. We will update this issue again once the roll back is completed, and we will provide further updates on when we will re-roll forward the feature once we feel enough 3rd party tools have been updated with support for the force flag.

Read the linked EKS upgrade insights and UpdateClusterVersion documentation, along with issue #2569, first. The announcement says it will be updated when the rollback is complete and later when the feature is re-enabled, but it names no repository file, test, or concrete contribution.

Written by the indexing model from the issue text.