Nodes are bootstrapped with WICD bootstrap command

Description

As part of the health management epic, WMCO will use WICD to initially create a node object, before the configuration continues. When this story is complete, all usage of WMCB will be removed, and WMCB itself should be removed from the payload. In order to run the WICD bootstrap command, the containerd and kubelet services must be expressed in the services ConfigMap, and have the `bootstrap` flag set to true. When the bootstrap command is ran, WICD will start said services, and once the proper CSRs are approved by WMCO, a Node object will be created.

Acceptance Criteria

• WMCO no longer invokes WMCB
• WMCO copies the kubelet-ca.crt and bootstrap kubeconfig files present within the ignition file, to the Windows instance
• WMCO makes use of the WICD bootstrap command to bootstrap nodes
• WMCO ensures that a Node object has been created
• Log levels are set accordingly when running WICD bootstrap so WMCO isn't flooded with logs