OCPNODE-2875: skip drain on new registry entry without mirrors

[QiWang19]

- What I did
openshift/runtime-utils#22 allows adding a new registry entry to registries.conf without using a mirror through ICSP, IDMS, or ITMS. The MirrorByDigestOnly setting does not affect image pulls from the primary registry with this new registry change.(openshift/runtime-utils#22 (comment)) Therefore, this PR removes the logic that caused node drain in this scenario.
- How to verify it

- Description for the changelog

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: QiWang19
Once this PR has been reviewed and has the lgtm label, please assign djoshy for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@QiWang19: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-vsphere-ovn-upi	1074f59	link	false	/test e2e-vsphere-ovn-upi
ci/prow/e2e-azure-ovn-upgrade-out-of-change	1074f59	link	false	/test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-hypershift	1074f59	link	true	/test e2e-hypershift

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@QiWang19: This pull request references OCPNODE-2875 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

- What I did
openshift/runtime-utils#22 allows adding a new registry entry to registries.conf without using a mirror through ICSP, IDMS, or ITMS. The MirrorByDigestOnly setting does not affect image pulls from the primary registry with this new registry change. Therefore, this PR removes the logic that caused node drain in this scenario.
- How to verify it

- Description for the changelog

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@QiWang19: This pull request references OCPNODE-2875 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

- What I did
openshift/runtime-utils#22 allows adding a new registry entry to registries.conf without using a mirror through ICSP, IDMS, or ITMS. The MirrorByDigestOnly setting does not affect image pulls from the primary registry with this new registry change.(openshift/runtime-utils#22 (comment)) Therefore, this PR removes the logic that caused node drain in this scenario.
- How to verify it

- Description for the changelog

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.