If the amount of images on a node is greater than 50 and nodeStatusMaxImages` wasn't set to `-1`, than the node will hit the issue described in https://github.com/openshift/openshift-docs/pull/41303/files and the pod scheduling might be imbalanced across nodes.

We need to add an alert when number of images on the node is greater then 50 and nodeStatusMaxImages` wasn't set to `-1` and provide the users with how to fix this issue.

This will also help us to understand the extent of the issue that was found in bug https://bugzilla.redhat.com/show_bug.cgi?id=1995518 and https://bugzilla.redhat.com/show_bug.cgi?id=1984442.

Since this is an OpenShift virtualization alert, we also limited this alert to fire when HCO is installed.