Following up on OTA-567, we should handle the case where a user installs a cluster, and subsequently modifies ClusterVersion's spec.capabilities in a way that stops asking for a previously-enabled capability.  We want to confirm that the ClusterVersion resource:

• Continues to reconcile all previously-enabled capabilities, including the one that spec.capabilities is no longer asking for, and declares the full set in status.capabilities.
• Reports that the divergence in a new status.conditions type. "Hey, you're not asking for capA anymore, but I'm going to keep reconciling it because I was reconciling some of those manifests before", or similar.