Add teleport-operator to mc-bootstrap

[tuladhar]

Deploy teleport-operator as part of MC creation to ensure creation of teleport join token before we pivot from Kind to infrastructure provider (AWS, GCP, etc).

[tuladhar]

As discussed with the team, we will be using short-lived certificate through Machine ID, teleport-operator no longer needs to be added to mc-bootstrap cause we won't be using static credential.

However, we get into chicken-egg problem, because cluster provider chart references a token which is created by teleport-operator, and since, Machine ID only works when Kubernetes API is ready, we will be creating a dummy teleport join token secret to unblock cluster provider chart, and later when teleport-operator is deployed via app collection, we roll out nodes again.

I think it's not ideal solution, but so far this is what we come up with, until we figure out a better way.

[tuladhar]

PR ready for review:

• https://github.com/giantswarm/mc-bootstrap/pull/702

✅ All generate MC checks are passing.