Revise how handler is structured

A couple of ideas while revising the current handler code, as it seems unnecessarily coupled at the moment.

• break the cycle between handler <-> feature builder to register/add features
• allow to define multi featureProviders for a single handler - this can decouple features per infra aspect (e.g. authz, mesh networking etc) -> that can lead to a single handler per operator instead of per component now.
• Apply could return structured info with more details
  • carry information about the originating component
  • flesh out how to update dsc/dsci status with those / investigate and task out to the new story
  • long way to have handler init/apply the only thing in the reconciles of components
    • current manifests apply as features
    • ...