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

@@ -29,7 +29,7 @@
     {
       "id": "data",
       "type": "directory",
-      "path": "/services/portainer/portainer_data",
+      "path": "/var/lib/portainer/data",
       "mode": "0700"
     },
     {
@@ -42,7 +42,7 @@
         "9443:9443"
       ],
       "volumes": [
-        "/services/portainer/portainer_data:/data",
+        "/var/lib/portainer/data:/data",
         "/var/run/docker.sock:/var/run/docker.sock"
       ]
     },