chore: Add flag for setting timeout for creating windows vms

[ksimon1]

What this PR does / why we need it:
some Windows images require more time to download image.
This commit adds new flag windows-ready-timeout, which
will allow user to set higher timeout only for Windows VMs.
All other OS distributions will use default timeout.

Release note:

NONE

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lyarwood for approval. For more information see the Kubernetes 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

[lyarwood]

Has this been reported as an issue downstream somewhere?

I assume the issue is mostly with the huge size of the DVs being created rather than the time the OS takes to start and become ready?

I'd much prefer to either have a dedicated constant for the impacted Windows tests or have the ability to pass in a custom timeout into the test binary somehow for downstream to manage this. That might even allow us to lower the timeout for the other tests from the current 5 minutes that seems excessive.

[ksimon1]

This came from my investigation when I tried the new images.
I added new flag windows-ready-timeout by which the user can set higher timeout only for Windows VMs.

[jcanocan]

/lgtm