wicked: set ifup timeout

[jpculp]

Description of changes:

This bumps the wicked ifup timeout from the default 30s to 300s.

Testing done:

• Build aws-k8s-1.20 x86_64 AMI and launch 30 instances.
• Build vmware-k8s-1.21 x86_64 and join to VMware cluster.
• Build aws-dev and launch VM that has no network interface. (thanks @bcressey!)

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

[jpculp]

I'll pull this out of draft after #1798 is merged.

[jpculp]

• Rebased
• Switched new timeout from infinite to 300s.

[etungsten]

lgtm assuming testing vmware passes

[zmrow]

🖌️

[bcressey]

I've tested this using aws-dev under QEMU with a VM that had no network interface:

Nov 03 15:47:09 localhost systemd[1]: Starting wicked managed network interfaces...
[  303.310291] early-boot-config[1421]: Provider error: IMDS client failed: Error PUTing 'http://169.254.169.254/latest/api/token': error sending requ)
Nov 03 15:52:09 localhost wicked[1417]: eth0            no-device
Nov 03 15:52:09 localhost systemd[1]: Finished wicked managed network interfaces.
Nov 03 15:52:09 localhost systemd[1]: Reached target Network.
Nov 03 15:52:09 localhost systemd[1]: Reached target Network is Online.
Nov 03 15:52:09 localhost systemd[1]: Starting Bottlerocket userdata configuration system...
Nov 03 15:52:09 localhost early-boot-config[1421]: 15:52:09 [INFO] early-boot-config started
Nov 03 15:52:09 localhost early-boot-config[1421]: 15:52:09 [INFO] Retrieving platform-specific data
Nov 03 15:52:09 localhost early-boot-config[1421]: Provider error: IMDS client failed: Error PUTing 'http://169.254.169.254/latest/api/token': error s)
Nov 03 15:52:09 localhost systemd[1]: early-boot-config.service: Main process exited, code=exited, status=1/FAILURE

So this timeout works as expected, although the output is misleading since wicked is returning successfully even though the interface isn't up.