fix(forgejo,vaultwarden): restart with postgresql

As it has been discovered, regular update of postgresql cause issues when
the database gets restarted, cause the containers can no longer correctly
resolve the hostname and reconnect, therefore use ‹PartOf› to truly¹
force a restart of the container once the database gets restarted.

¹ Tried to fix a similar issue once already in 737acfd, based on the
  observations, I have failed…

Signed-off-by: Matej Focko <me@mfocko.xyz>

roles/forgejo/templates/forgejo.container

@@ -4,6 +4,7 @@
 Description=Forgejo
 After=postgresql.service
 Requires=postgresql.service
+PartOf=postgresql.service
 
 [Container]
 ContainerName=forgejo

roles/vaultwarden/templates/vaultwarden.container

@@ -4,6 +4,7 @@
 Description=Vaultwarden
 After=postgresql.service
 Requires=postgresql.service
+PartOf=postgresql.service
 
 [Container]
 ContainerName=vaultwarden