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/mesh-watcher/files/settings.json

@@ -0,0 +1,3 @@
+{
+  "telegram-chat-id": ""
+}

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

@@ -18,20 +18,30 @@
     "watcher_test",
     "watcher_ping"
   ],
+  "config": {
+    "telegram-chat-id": {
+      "type": "string",
+      "description": "The Telegram chat the watcher reports to: the chat's id, a number, or @name of a channel; empty reports to none.",
+      "trusted": true,
+      "default": ""
+    }
+  },
   "resources": [
     {
       "id": "state",
       "type": "directory",
       "mode": "0700",
-      "place": "."
+      "place": ".",
+      "unknown": "program"
     },
     {
       "id": "settings",
       "type": "file",
       "path": "${dir:state}/settings.json",
       "mode": "0600",
+      "takes-config": ["telegram-chat-id"],
       "merge": "json",
-      "content": "{\n  \"telegram-chat-id\": \"\"\n}\n"
+      "template": "files/settings.json"
     }
   ],
   "build": {
@@ -50,6 +60,11 @@
           "MESH_WATCHER_SETTINGS": "${dir:state}/settings.json",
           "MESH_WATCHER_TELEGRAM_TOKEN_FILE": "${dir:state}/telegram-token"
         }
+      },
+      {
+        "name": "files",
+        "kind": "archive",
+        "from": "files"
       }
     ]
   }