feat: add conditions to status subresource on CRs

[rafalgalaw]

TODO:

• Add more tests
• remove unecessary status update calls

[bavarianbidi]

From a pool-perspective the following conditions (with state False, True and Unknown) make sense:

• ImageReference

  • False if the referenced image doesn't exist
  • True if the referenced image exist

  Reason/Message: whatever we have by hand :-)

• PoolReady

  • False if the pool exist in garm but pool-manager is false
  • True if pool-manager is ready

  Reason/Message: whatever we have by hand from garm-response - e.g the LastSyncError string?

• ScopeReference (in the future)
  if we want to decouple the scopereference in the poolCR (by removing the validation) - to make cr-creation idempotent

[bavarianbidi]

the conditions itself are looking fine. +1 for that.

we should "batch" all the changes and do r.Status().Update(... at the end of the reconciliation loop. On the mid-term we should move to patches and with that we do not change the CRs that often if nothing has changed.

otherwise we are doing tons of updates which means, every CR will get added to the reconcile loop immediately ( we had the same/similar issue when we've set the last-reconcile timestamp in the status)