Workaround for 4.4 etcd operator addition

OpenShift 4.4 added an operator managing etcd instances on the cluster which mandates the use of at least 3 nodes, and aborts if not. This causes installation failures when using snc. These failures can be avoided by running the command below as soon as the bootstrap API server is up:

$ oc patch etcd cluster -p='{"spec": {"unsupportedConfigOverrides": {"useUnsupportedUnsafeNonHANonProductionUnstableEtcd": true}}}' --type=merge

The kubeconfig file to use is in crc-tmp-install-data/auth/kubeconfig The following lines are logged when the API server is up:

level=debug msg="Still waiting for the Kubernetes API: Get https://api.crc.testing:6443/version?timeout=32s: dial tcp 192.168.126.11:6443: connect: connection refused"
level=debug msg="Still waiting for the Kubernetes API: Get https://api.crc.testing:6443/version?timeout=32s: net/http: TLS handshake timeout"
level=info msg="API v1.18.0-rc.1 up"
level=info msg="Waiting up to 40m0s for bootstrapping to complete..."