Decouple adding new static worker nodes from the installation process

[xmudrii]

Description of the feature you would like to add / User story

Adding a new static worker node initiates the whole cluster provisioning process. This means that it might upgrade packages on control plane nodes (such as containerd, crictl...) which might not be expected when adding a new worker node. I think adding new worker nodes should be a decoupled process that doesn't touch control plane nodes at all besides generating the needed kubeadm token.

Solution details

• Add a dedicated task only for adding new static worker nodes

Alternative approaches

There's no alternative available to avoid touching control plane nodes when adding new static worker nodes

Use cases

• Users get to better plan their maintenance window and when they want to upgrade components on control plane nodes