Get status.conditions from CAPI operator during updateComponentsStatus

[squizzi]

In this PR we now update our component statuses by iterating the provider CRDs affiliated with CAPI operator and returning a status error if any of the status.conditions are False or if we cannot obtain any information pertaining to status condition. For example:

In this case cluster-api-provider-aws and -azure are not yet installed:

  status:
    availableProviders: {}
    components:
      cluster-api:
        success: true
      cluster-api-provider-aws:
        error: 'failed to find any provider resources affiliated with template: cluster-api-provider-aws'
      cluster-api-provider-azure:
        error: 'failed to find any provider resources affiliated with template: cluster-api-provider-azure'
      hmc:
        success: true
      k0smotron:
        success: true

In this case cluster-api-provider-aws is reporting some status conditions false:

  status:
    availableProviders: {}
    components:
      cluster-api:
        success: true
      cluster-api-provider-aws:
        error: 'InfrastructureProvider: aws is not yet ready, has false conditions: MinimumReplicasAvailable'
      cluster-api-provider-azure:
        success: true
      hmc:
        success: true
      k0smotron:
        success: true

In this case cluster-api-provider-aws has no status.conditions because something is going wrong. Perhaps we could add some additional statuses for special circumstances; here it's because aws-variables does not yet exist yet, but I couldn't find anyway to assume this type of circumstance, capi-operator doesn't produce any event in this case, it only generates a log.

    components:
      cluster-api:
        success: true
      cluster-api-provider-aws:
        error: 'failed to get status for template: cluster-api-provider-aws: failed
          to get conditions: no status conditions found for InfrastructureProvider:
          aws'
      cluster-api-provider-azure:
        success: true
      hmc:
        success: true
      k0smotron:
        success: true

Closes #235

[squizzi]

I can probably add some unit tests to this using envtest, I just wanted to get some thoughts/eyes on before I do that.

Edit: This apparently isn't trivial to test in envtest, perhaps I could add an e2e test to the controller suite, I'm working on breaking the providers/controllers tests apart for the vsphere tests to work right anyways so that might work well.

[squizzi]

I'll plan to add an e2e test in a follow-up once the controller tests have been refactored as part of #360

Addressed

[a13x5]

Some resolved conversations aren't resolved for some reason.
Several other notes, mostly minor

[squizzi]

@eromanova another rebase cleared your review, if you don't mind approving again

Addressed