Add delay after patching the current host

[dhoogfr]

Add delay after patching the current host, before continuing with the next host

After patching a host, it takes some time before that host (after rebooting) is a valid target again for guests to be migrated to.
With a 2 node cluster, this can cause the patching of the second host to fail because the guests cannot be migrated of that host or to cause the guests to be shutdown (depending on the used parameters).
This can be avoided by adding a delay (controlled by the wait_before_next_upgrade parameter, defaulting to 5 minutes) before continuing with the next host

[dhoogfr]

Hi,

I noticed that one build failed because of a missing changelog?
Do I need to provide something for this?

[mnecas]

Hi @dhoogfr,
thanks for the patch!
I'm not sure about the use-case(don't like to see adding wait).
If the host upgrade starts before it should I think it should be addressed in the ovirt_host module when sending the upgrade request and waiting for it to finish.
(the gluster delay is for specific case)
https://github.com/oVirt/ovirt-ansible-collection/blob/master/plugins/modules/ovirt_host.py#L584