Bug#1023557: rygel: consider After=network.target in rygel.service for lingering

[Barak A. Pearlmutter]

Okay, here's a manifestation of some network-change rygel-stops issue.
This is rygel 0.42.0-2.
Logs below.
After "systemctl --user restart rygel.service" it works fine.

$ last -1 reboot
reboot   system boot  6.0.0-6-amd64    Wed Dec 21 09:00   still running

$ systemctl --user status rygel.service
○ rygel.service - Rygel DLNA/UPnP server
     Loaded: loaded (/usr/lib/systemd/user/rygel.service; enabled;
preset: enabled)
     Active: inactive (dead) since Wed 2022-12-21 09:00:46 GMT; 13min ago
   Duration: 30.065s
    Process: 853 ExecStart=/usr/bin/rygel (code=exited, status=0/SUCCESS)
   Main PID: 853 (code=exited, status=0/SUCCESS)
        CPU: 6.485s

Dec 21 09:00:20 sweat rygel[853]: Error sending SSDP packet to
FF0E::C: Error sending message: Network is unreachable
Dec 21 09:00:20 sweat rygel[853]: Error sending SSDP packet to
FF0E::C: Error sending message: Network is unreachable
Dec 21 09:00:20 sweat rygel[853]: Error creating GUPnP context: Failed
to bind socketError binding to address
[fe80::4f84:2ae9:bb96:f67f%3]:1900: Cannot assign requested address
Dec 21 09:00:46 sweat systemd[811]: Stopping Rygel DLNA/UPnP server...
Dec 21 09:00:46 sweat rygel[853]: Process check_async failed: Child
process killed by signal 15
Dec 21 09:00:46 sweat rygel[853]: g_file_new_for_uri: assertion 'uri
!= NULL' failed
Dec 21 09:00:46 sweat rygel[853]:
rygel_media_export_harvesting_task_on_extractor_error_cb: assertion
'file != NULL' failed
Dec 21 09:00:46 sweat mx-extract[2354]:
rygel-media-export-extract.vala:180: Started with descriptors 3 (in) 4
(out), extracting meta-data: true
Dec 21 09:00:46 sweat systemd[811]: Stopped Rygel DLNA/UPnP server.
Dec 21 09:00:46 sweat systemd[811]: rygel.service: Consumed 6.485s CPU time.