EKS 1.23 to 1.24 Upgrade Concerns

I am being forced to upgrade my EKS clusters from version 1.23 to 1.24 and I have a question. The documentation AWS provides lacks some more insights on this.

Will clicking the "Upgrade now" button automagically make all of our nodes in the cluster run on containerd once the upgrade is concluded, or are we required by EKS to first:

1. Create a new node group (we currently run 4 node groups and 9 nodes in total).
2. Apply a taint to the old node group to deprovision them with new instances in the new node group.
3. Delete our old compute node group once no more containers are running on it ?

In addition, my infrastructure depends on some deprecated, non-standard, beta, or unofficial API versions. I need to know if these will break when updating to version 1.24. The following are the APIs in question:

• bitnami.com/v1alpha1
• monitoring.coreos.com/v1
• keda.sh/v1alpha1
• eksctl.io/v1alpha5
• source.toolkit.fluxcd.io/v1beta1
• helm.toolkit.fluxcd.io/v2beta1
• snapshot.storage.k8s.io/v1
• rbac.authorization.k8s.io/v1
• notification.toolkit.fluxcd.io/v1beta1
• image.toolkit.fluxcd.io/v1beta1
• kustomize.config.k8s.io/v1beta1
• networking.k8s.io/v1

I appreciate any help you can provide.