[DNM] Added Templates to test cluster upgrade

[eromanova]

Added new aws and azure standalone clustertemplates that can be used for testing managed cluster upgrades:

All cluster updates were tested with 2 control plane and 2 worker machines with these configurations: https://github.com/Mirantis/hmc/blob/main/config/dev/aws-managedcluster.yaml
https://github.com/Mirantis/hmc/blob/main/config/dev/azure-managedcluster.yaml

1. ✅ aws-standalone-0-0-2
   Upgrade 0.0.1 -> 0.0.2:
   Diff:
   • aws-ebs-csi-driver: bumped 2.33.0 -> 2.35.1
   • aws-cloud-controller-manager: enabled more verbose logging (v=2 -> v=10)
2. ❌ [Does not work ATM. Calico crashes] aws-standalone-0-0-3
   Upgrade 0.0.1 -> 0.0.3:
   Diff:
   • k0s version update: v1.30.4+k0s.0 -> v1.31.1+k0s.0
3. ✅ azure-standalone-0-0-2
   Upgrade 0.0.1 -> 0.0.2:
   Diff:
   • Added new test label on the machine deployment template
4. ✅ azure-standalone-0-0-3
   Upgrade 0.0.1 -> 0.0.3:
   Diff:
   • k0s version update: v1.30.4+k0s.0 -> v1.31.1+k0s.0

The following TemplateManagement and ClusterTemplateChain configurations can be used for testing:

---
apiVersion: hmc.mirantis.com/v1alpha1
kind: ClusterTemplateChain
metadata:
  name: test
  namespace: hmc-system
spec:
  supportedTemplates:
    - name: aws-standalone-cp-0-0-1
      availableUpgrades:
        - name: aws-standalone-cp-0-0-2
       # Commented since it does not work yet
       # - name: aws-standalone-cp-0-0-3
    - name: aws-standalone-cp-0-0-2
    - name: aws-standalone-cp-0-0-3
    - name: azure-standalone-cp-0-0-1
      availableUpgrades:
        - name: azure-standalone-cp-0-0-2
        - name: azure-standalone-cp-0-0-3
    - name: azure-standalone-cp-0-0-2
    - name: azure-standalone-cp-0-0-3
---
apiVersion: hmc.mirantis.com/v1alpha1
kind: TemplateManagement
metadata:
  name: hmc
spec:
  accessRules:
  - targetNamespaces:
      list:
        - default
    clusterTemplateChains:
      - test

Documentation: Mirantis/project-2a-docs#11

[eromanova]

Testing discovered k0sproject/k0smotron#780
Azure managed cluster update that affects k0sconfig changes does not work due to the bug.