Module data lives in /var/lib, now that nothing is mid-cutover

The /services paths were the adopted-node pattern doing its job: take
replaced containers over the predecessor's data without moving a byte
(gitea set it — 'its data never moved'). With every cutover done the
exception has no reason left, and the operator called it: a nox
module's world is /var/lib/<module>, data included. Six modules
repathed; mssql keeps its /services path deliberately — it is still
held, HAL-run, and moves at its own take. Both trees are one
filesystem, so each move is a rename.

modules/gitea/module.json

@@ -121,7 +121,7 @@
     {
       "id": "data",
       "type": "directory",
-      "path": "/services/gitea/gitea",
+      "path": "/var/lib/gitea/data",
       "mode": "0700",
       "owner": "1000:1000"
     },
@@ -143,7 +143,7 @@
         "222:22"
       ],
       "volumes": [
-        "/services/gitea/gitea:/data"
+        "/var/lib/gitea/data:/data"
       ],
       "secrets-in-environment": "gitea honours GITEA__database__PASSWD__FILE and GITEA__security__INTERNAL_TOKEN__FILE; convertible, awaiting a bed that proves it"
     },
@@ -162,7 +162,7 @@
         "/var/lib/gitea/server.env"
       ],
       "volumes": [
-        "/services/gitea/gitea:/data",
+        "/var/lib/gitea/data:/data",
         "/var/lib/gitea/admin.secret:/run/secrets/admin:ro"
       ],
       "args": [