Bug 2000787

+++ This bug was initially created as a clone of Bug #1995684 +++

Description of problem:
Adding a BYOH node using a DNS address that is different than the hostname results in an error such as:
```
2021-08-19T15:05:54.094Z	DEBUG	controller-runtime.manager.events	Warning	{"object": {"kind":"ConfigMap","namespace":"openshift-windows-machine-config-operator","name":"windows-instances","uid":"29d12cf0-eb29-4712-ba56-7e27e99a899a","apiVersion":"v1","resourceVersion":"525987"}, "reason": "InstanceSetupFailure", "message": "error configuring host with address dhcp-host-90.cloud.chx: error getting node object: unable to find node with address dhcp-host-90.cloud.chx: timed out waiting for the condition"}
```

This is due to the node status object not having the given address present in it:
```
status:
  addresses:
  - address: 192.168.1.90
    type: ExternalIP
  - address: 192.168.1.90
    type: InternalIP
  - address: dhcp-host-90
    type: Hostname
```

This can be worked around by using the instance's IP address in the windows-instances ConfigMap instead.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Try to configure a BYOH Windows instance using a DNS address that is different from the instance's hostname.
2. The error will appear in the WMCO logs and/or the windows-instance ConfigMap events.

Actual results:
Error as seen above

Expected results:
No error, instance is fully configured as a node.

Additional info:
This can be fixed by doing a DNS lookup of the address, and using the IP to locate the node.