nmstate.service has been recently shipped with `Requires=` dependency on NetworkManager-wait-online. This fails in various OpenShift deployments as the latter very often fails in baremetal deployments.

As a result, we get systems with nmstate.service failing and as a result, static network configuration may not be applied on those.

This is also kinda circular dependency in case we need nmstate.service to apply a configuration that is needed for the network to be fully functional.

Ultimately, we'd recommend that nmstate.service only wants but not requires NetworkManager-wait-online.

This is a regression introduced in v2.2.48 and fixed in 2.2.52
https://github.com/nmstate/nmstate/releases/tag/v2.2.48
https://github.com/nmstate/nmstate/releases/tag/v2.2.52