🐛 fix: missing MaxActiveUpdateDeleteWait in managednodegroup scope

[damdo]

What type of PR is this?

/kind bug

What this PR does / why we need it:

#5498 missed propagating the MaxActiveUpdateDeleteWait to the managednodegroup scope, resulting in a zero value which made the wait fail, which in turn always failed the E2E.

Which issue(s) this PR fixes:
Fixes #5514

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/release-note-none

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[richardcase]

Feel free to unhold when the e2e pass:

/hold

[richardcase]

Thanks for this @damdo

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: f51d046118b27872a8e1f1e15fd5dde97ba48baa

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardcase

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [richardcase]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[damdo]

Tests passed 🎉

/unhold

[dlipovetsky]

/cherrypick release-2.8

[k8s-infra-cherrypick-robot]

@dlipovetsky: #5554 failed to apply on top of branch "release-2.8":

Applying: fix: missing maxActiveUpdateDeleteWait in managednodegroup scope
Using index info to reconstruct a base tree...
M	pkg/cloud/scope/managednodegroup.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/cloud/scope/managednodegroup.go
CONFLICT (content): Merge conflict in pkg/cloud/scope/managednodegroup.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 fix: missing maxActiveUpdateDeleteWait in managednodegroup scope

In response to this:

/cherrypick release-2.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[damdo]

@dlipovetsky IIUC #5498 which introduced this is only in main and not in any v2.8.z or in release-2.8
So do we need to backport this?

[dlipovetsky]

@dlipovetsky IIUC #5498 which introduced this is only in main and not in any v2.8.z or in release-2.8 So do we need to backport this?

I'm sorry--not what I wanted to do. I wanted to backport #5517 to release-2.8