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/nextcloud/module.json

@@ -67,7 +67,7 @@
     {
       "id": "html",
       "type": "directory",
-      "path": "/services/nextcloud/html",
+      "path": "/var/lib/nextcloud-module/html",
       "mode": "0750",
       "owner": "33:33"
     },
@@ -83,7 +83,7 @@
         "80"
       ],
       "volumes": [
-        "/services/nextcloud/html:/var/www/html"
+        "/var/lib/nextcloud-module/html:/var/www/html"
       ],
       "secrets-in-environment": "the image honours POSTGRES_PASSWORD_FILE and NEXTCLOUD_ADMIN_PASSWORD_FILE (entrypoint file_env); OBJECTSTORE_S3_SECRET has none and needs a generated config fragment; convertible, awaiting a bed"
     },