[EKS] [request]: Support customizing updateStrategy on vpc-cni DaemonSet

### 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 want to be able to add customized `updateStrategy` block into the `configuration_values` of the vpc-cni addon.

**Which service(s) is this request for?**
EKS, vpc-cni addon

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We want to speed up the rollingUpgrade of `aws-node` DaemonSet, especially when dealing with large clusters.

**Are you currently working around this issue?**
N/A

**Additional context**
N/A

**Attachments**
N/A

Start by tracing how the EKS vpc-cni add-on consumes configuration_values and how the aws-node DaemonSet updateStrategy is represented. Confirm the supported customization boundary and define the expected rollingUpgrade behavior for large clusters; no repository files or tests are identified in the issue.

Written by the indexing model from the issue text.