CRD will convey structed data about both Customer Build Image and Final Build Images for all pools that use layering.

This will allow customer, support, team to easily inspect what layering is in effect in a cluster without manual intervention on a node. This will also be used by console team to pipe info into the webui. Will also allow use to pull this info into a must gather.

Keep in mind: there may be more than 1 Customer Base Image at a time (we accommodate a 2 version kubelet apiserver skew) and different pools may have different hotfixes/custom layers

Longterm: crd/controller design should be extensible into multple namespaces for non-stock generic OCP deployments (this might need it's own card).