Ten migration-critical modules become mesh-buildable (issue 060)

keycloak, mailu, minio, mongodb, mssql, nextcloud, portainer, redis,
umami and verdaccio get the Dockerfile + build section the eight
buildable modules already had; their runtime containers name the
artifact instead of a placeholder digest.

One convention, settled (060's open question, informed by 061): the
runtime container runs serve mode with every serve-time entrypoint in
MESH_TOOL_MODULES — tools serve, events flow, and a provider's
provisioner reconciles in the same process with the broker connected.
postgres, gitea and lavinmq are retrofitted from args-run provisioners,
which served no tools and emitted lifecycle events nowhere.

route-proxy is deferred: its build context is the mesh-controller
repository, a cross-repo shape the build section cannot yet express.

modules/lavinmq/module.json

@@ -107,11 +107,7 @@
         "MESH_PROVISION_LAVINMQ": "http://127.0.0.1:15672",
         "MESH_PROVISION_ADMIN_USER": "guest",
         "MESH_LAVINMQ_ADMIN_PASSWORD": "guest"
-      },
-      "args": [
-        "run",
-        "/app/modules/lavinmq/dist/provisioner/index.js"
-      ]
+      }
     }
   ],
   "build": {