Bug: validateCredentialsNumber is also called when no fencing config is present

[jm-dt]

Our test deploying using OCP 4.19.0-rc.0 fails to install with the message "Forbidden: there should be exactly two fencing credentials to support the two node cluster, instead 0 credentials were found". We do not have a fencing config in our installation configuration.

We assume that this line should only be called when a fencing config is actually present.

[jm-dt]

We understand that this only happens if the number of nodes is two.