MGMT-15878: Add a condition to show the last preparation failure (ope…

…nshift#5524)

Presently when installing a cluster, there is no indication of the reason for the last failure in preparation.
We record the fact that a failure occurred in that database field `cluster.installation_preparation_completion_status` but we do not store any
reason for the failure.

We are adding the field `cluster.installation_preparation_completion_status_reason` so that we may record the reason at the same time an
event is generated.

The content of `cluster.installation_preparation_completion_status` and `cluster.installation_preparation_completion_status_reason` are used to
determine the state of a newly created condition `LastInstallationPreparationFailed`

api/hiveextension/v1beta1/agentclusterinstall_types.go

@@ -79,6 +79,11 @@ const (
 	ClusterBackendErrorMsg    string = "The Spec could not be synced due to backend error:"
 	ClusterInputErrorReason   string = "InputError"
 	ClusterInputErrorMsg      string = "The Spec could not be synced due to an input error:"
+
+	ClusterLastInstallationPreparationFailedOKReason    string = "There is no failing prior preparation attempt"
+	ClusterLastInstallationPreparationFailedErrorReason string = "The last installation preparation failed"
+	ClusterLastInstallationPreparationPending           string = "Cluster preparation has never been performed for this cluster"
+	ClusterLastInstallationPreparationFailedCondition   string = "LastInstallationPreparationFailed"
 )
 
 // +genclient