rootless podman units should wait for podman-user-wait-network-online.service

[Luap99]

Issue Description

In #24305 I made quadlet units wait for podman-user-wait-network-online.service, however the same network startup issue still exists for our static podman units that start containers such as podman-restart.service and [email protected].
They should use the same After=podman-user-wait-network-online.service in the rootless case to make them work the same.

Steps to reproduce the issue

Steps to reproduce the issue

1. Have lingering enabled and try to start a container via podman-restart.service on boot before the network is ready, see Podman fail to autostart containers through quadlet/systemd, works when launched manually, error with pasta #22197

Describe the results you received

pasta failed to start as the network was not yet ready

Describe the results you expected

unit should start after the network is ready

podman info output

podman 5.3.0

Podman in a container

No

Privileged Or Rootless

Rootless

Upstream Latest Release

Yes

Additional environment details

No response

Additional information

Needs a slow network setup to reproduce (I was able to trigger this by reassigning new mac address to libvirt VMs then on the next boot network setup took several seconds which was long enough to start the user unit to early when lingering is enabled)

[github-actions]

A friendly reminder that this issue had no activity for 30 days.