Description of problem:
Currently, there is only 1 condition type under UOCR (as far as I see) for various error checks and the overall status, and the timestamp only changes when the the condition status changed/upgrade is completed. (This is standard behavior from meta after talking with Irina).
 
It would be best to split some of the validations out and add different stages so user knows what has been validated and what is currently being done. 

Some examples for additional condition types: 
- Ready  -> for overall status like it currently has
- SpecValidated -> Check spec format, required fields, etc
- CandidateClusersExist -> Checks if any spokes should be upgraded, and Ready status should become True if all clusters are already compliant, and reason could be "No cluster to upgrade"
- Started -> true if enforce policies were created for individual clusters, false if blocked by blockingCR etc.
- Stopped -> true if canaries failed, etc; false for in-progress or completed.

Version-Release number of selected component (if applicable):
4.10

How reproducible:
100%

Steps to Reproduce:
1. Create and enable UOCR with blockingCR
2. Observe UOCR status changes

Actual results:
Only 1 condition available while state changes, e.g., it was first blocked due to missing blockingCR, then waiting for blocking CR to finish, then started upgrade and waiting for policies to be compliant. But the lastTransitionTime does NOT change until status changed from False to True, this is confusing to user.

  conditions:
  - lastTransitionTime: "2022-01-19T17:53:22Z"
    message: The ClusterGroupUpgrade CR has all clusters compliant with all the managed
      policies
    reason: UpgradeCompleted
    status: "True"
    type: Ready


Expected results:
Better/More information is provided by UOCR conditions


Additional info: