feat: component API based node bootstrapping

[bcho]

This pull request implemented the base sets of component API for bootstrappign a linux node to join to AKS as flex node. We introduced a new sub command apply -f for applying one time config.

Sample configurations:

[
  {
    "metadata": {
      "type": "aks.flex.components.linux.ConfigureBaseOS",
      "name": "configure-base-os"
    },
    "spec": {}
  },
  {
    "metadata": {
      "type": "aks.flex.components.cri.DownloadCRIBinaries",
      "name": "download-cri-binaries"
    },
    "spec": {
      "containerd_version": "2.0.4",
      "runc_version": "1.2.5"
    }
  },
  {
    "metadata": {
      "type": "aks.flex.components.kubebins.DownloadKubeBinaries",
      "name": "download-kube-binaries"
    },
    "spec": {
      "kubernetes_version": "1.32.3"
    }
  },
  {
    "metadata": {
      "type": "aks.flex.components.cri.StartContainerdService",
      "name": "start-containerd-service"
    },
    "spec": {}
  },
  {
    "metadata": {
      "type": "aks.flex.components.kubeadm.KubadmNodeJoin",
      "name": "kubeadm-node-join"
    },
    "spec": {
      "control_plane": {
        "server": "<cluster-endpoint>",
        "certificate_authority_data": "<ca>"
      },
      "kubelet": {
        "bootstrap_auth_info": {
          "token": "<token>"
        },
        "node_labels": {
          "kubernetes.azure.com/managed": "false",
          "kubernetes.azure.com/cluster": "<value>"
        }
      }
    }
  }
]

Sample output from local vm:

ubuntu@flexnode-vm:/flex-node$ sudo ./aks-flex-node apply -f component-config.json

  configure-base-os             7.9s  ok
  download-cri-binaries         1.7s  ok
  download-kube-binaries        2.6s  ok
  start-containerd-service     323ms  ok
  kubeadm-node-join             9.2s  ok

  5 action(s) in 21.6s — all passed
ubuntu@flexnode-vm:/flex-node$

cluster side:

$ k get node
NAME                                 STATUS     ROLES    AGE    VERSION
...
flexnode-vm                          NotReady   <none>   39s    v1.32.3

---

Please note that, the component-config.json serves as a low level internal config. The existing config.json will be preserved and still be used by end user.

We will work on the migrations and adding test coverages in the follow up PRs