[EKS][Feature Request]: Improved Managed Nodegroup Upgrade Experience

### 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

**Tell us about your request**
We are wanting a more elegant way of handling Managed Nodegroup Upgrades by specifying which nodes in the nodegroup to update in a preferred order. This is for better handling of nodegroup upgrades that fail due to pod disruption budgets (PDBs) that interfere with the nodegroup upgrades.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
According to the [documentation](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-update-behavior.html#managed-node-update-upgrade), the upgrade process randomly selects a node that needs to be upgraded. The preferred mechanism would enable users to prioritize the order of which nodes will be upgraded first.

**Are you currently working around this issue?**
We are required to use the force update option, which ignores PDBs.

**How are you currently solving this problem?**
We have to use the force update option or delete the pods with PDBs manually.

Start with the linked AWS EKS managed node update behavior documentation and compare it with the requested preferred node order. Clarify the expected ordering mechanism and how it should interact with pod disruption budgets and forced updates. Done should mean a scoped EKS roadmap requirement with clear upgrade-order and PDB behavior.

Written by the indexing model from the issue text.