Migration CLI - IMDS v1/v2 settings migration

[T-Kukawka]

User Story

Starting with Vintage release 19.3.3 it is possible to specify the v1+v2 versus only v2 IDMS usage. Enabling IMDS v2 only support for the EC2 instances can be set via an annotation alpha.aws.giantswarm.io/metadata-v2: required on AWSMachineDeployment (for nodepools) and to AWSControlPlane (for control-plane nodes).

We have to take this into account for Vintage to CAPA migration. The values should be the same for both, master and workers, if any setting is present.

In Capa this can be set as following: https://github.com/giantswarm/roadmap/issues/3403

Acceptance Criteria

• [ ] migration cli will respect the Vintage annotation for metadata-v2 required and will also migrate this setting towards CAPA clusters
• [ ] if the annotation is not set, migration-cli will change the CAPA default from IMDSv2 only usage to have support for both, v1 and v2.

Dependencies (optional)

• https://github.com/giantswarm/roadmap/issues/3403

Implementation details

• Implementation info to be filled out by engineer