Restart behaviour of the VM daemon

Both in the Docker instructions

```
docker run -d --name=gvisor-tap-vsock --privileged --net=host -it quay.io/crcont/gvisor-tap-vsock:latest
```

and in [SNC](https://github.com/code-ready/snc/blob/68092c648474a1ce62d2d8ee1a34956b19c0a49b/createdisk.sh#L126)

```
podman generate systemd --restart-policy=no gvisor-tap-vsock > /etc/systemd/system/gvisor-tap-vsock.service
```

there is no restart policy. What if the daemon crashed? On several occassions I have been unable to connect to the VM when a restart was performed with a running host daemon: `crc daemon&; crc start; crc delete -f; crc start`

Review the Docker instructions and the SNC createdisk.sh entry at line 126, then trace how the generated gvisor-tap-vsock service behaves when the daemon exits or the host is restarted. Check the restart sequence described in the issue. Done means the documented or generated service reliably recovers from daemon failure and does not leave VM connections unusable after restart.

Written by the indexing model from the issue text.