OCM does not supply sufficient status for MachinePools

[scottd018]

In order for this operator to be able to tell if an OCM MachinePool is ready, the MachinePool in OCM should supply sufficient status to let us know when it is ready.

As a workaround, we are going to make the assumption (and the restriction) that this operator may only control itself in OCM. By doing this, we can poll the local nodes via the Kubernetes API and see when they are ready.

At some point in the future, it would be nice to have a centralized operator that could control machine pools from anywhere, thus the need for the status being available in OCM.