[epic] Add retry limits and a new reason to the `Progressing` status condition that is present when retry limit is reached.

As part of the v1 API stabilization effort, a few of us (@joelanford @grokspawn @LalatenduMohanty and I) identified that it would be a better user experience if the Progressing condition when set to True was considered a "happy" state where generally everything is okay and we are actively attempting to progress towards a future state OR are at the desired state and ready to progress towards any future desired states. We felt that Retrying is currently a mix of a "sad" and "happy" reason but is generally more reflective of "we encountered a hiccup in progressing" as opposed to requiring user intervention.

In an effort to make the Retrying reason be considered "happier", it was concluded that it would be best to add some form of a retry limit that when reached would result in the Progressing condition being set to False with a reason along the lines of RetryLimitExceeded to signal to users that the ClusterExtension/ClusterCatalog is no longer in a "happy" state.

Start by reviewing how ClusterExtension and ClusterCatalog currently set the Progressing condition and handle retries. Define the retry-limit behavior and the RetryLimitExceeded reason described in the issue, then add coverage showing the condition changes when the limit is reached.