Capture mesh-catalog at feat/r4g (2246ccc4) with the templates its manifests name and its predefined.json, and lay the copy out as a repository's root

The catalogue's manifests moved their content into template files and fall back to predefined keys, so a copy of
module.json alone no longer passes the catalogue's own check; the bus's Dockerfile is gone from the catalogue.

testdata/beside/mesh-catalog/modules/sshd/files/10-mesh.conf

@@ -0,0 +1,10 @@
+# Managed by the mesh (module sshd). Replaced on every push; edit the catalogue instead.
+Port 22
+PermitRootLogin no
+PasswordAuthentication no
+PubkeyAuthentication yes
+KbdInteractiveAuthentication no
+UsePAM yes
+X11Forwarding no
+PrintMotd no
+AcceptEnv LANG LC_*

testdata/beside/mesh-catalog/modules/sshd/module.json.captured

@@ -29,7 +29,7 @@
       "type": "file",
       "path": "/etc/ssh/sshd_config.d/10-mesh.conf",
       "mode": "0644",
-      "content": "# Managed by the mesh (module sshd). Replaced on every push; edit the catalogue instead.\nPort 22\nPermitRootLogin no\nPasswordAuthentication no\nPubkeyAuthentication yes\nKbdInteractiveAuthentication no\nUsePAM yes\nX11Forwarding no\nPrintMotd no\nAcceptEnv LANG LC_*\n"
+      "template": "files/10-mesh.conf"
     },
     {
       "id": "run",
@@ -41,5 +41,14 @@
         "config"
       ]
     }
-  ]
+  ],
+  "build": {
+    "artifacts": [
+      {
+        "name": "files",
+        "kind": "archive",
+        "from": "files"
+      }
+    ]
+  }
 }