Add the following alerts:

• CDINoDefaultStorageClass - not having a default (or virt default) storageClass is surely not an OpenShift error, as admins may prefer their cluster users to only use explicit storageClass names. However, in the CDI context when DV is created with default storageClass but default does not exist, we will fire an error event and the PVC will be Pending for the default storageClass, so when there are such Pending PVCs we will fire an alert (as suggested by rhn-engineering-jsafrane from OCP storage).
• CDIDefaultStorageClassDegraded - when the default (or virt default) storageClass does not support CSI/Snapshot clone (smart clone) or does not have ReadWriteMany access mode (for live migration).
• CDIStorageProfilesIncomplete - add storageClass and provisioner labels (as suggested by sradco), see CNV-28958.
• CDIDataImportCronOutdated - add dataImportCron name label, see CNV-28956.