Scratch notes:

• Is this "workload" or "config" per https://github.com/openshift/enhancements/blob/master/dev-guide/api-conventions.md#configuration-vs-workload-apis ?
• Initially just include Status. Future-looking thoughts from trking: isolating this spoke config object from the spoke user's ability to muck with it, since it's a control plane-oriented thing in HCP-land. More below...
• Is there a potential risk if the customer manages to hack the (to them, local) clusterversion object and their changes make it up to the hub?
• In alternatives (inlined in CD/HostedCluster), include considerations of etcd object size.