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/ssh-client/files/config

@@ -0,0 +1,6 @@
+# The mesh's region (module ssh-client, novox/hq research 027/03). It comes first because ssh
+# takes the first value it finds for each option. It brings in ~/.ssh/config.d/ in name order:
+# 00-mesh, the mesh's Host per machine, then each file another module places there. Replaced at
+# every push. Everything below it is yours, kept as you wrote it, and applies to every host the
+# files above leave unsettled.
+Include ~/.ssh/config.d/*

testdata/beside/mesh-catalog/modules/ssh-client/files/forge

@@ -0,0 +1,7 @@
+Host ${bound:forge-account:ssh_alias}
+  HostName ${bound:forge-account:ssh_host}
+  Port ${bound:forge-account:ssh_port}
+  HostKeyAlias ${bound:forge-account:ssh_alias}
+  User git
+  IdentityFile ~/.ssh/mesh_ed25519
+  IdentitiesOnly yes

testdata/beside/mesh-catalog/modules/ssh-client/files/gitconfig

@@ -0,0 +1,2 @@
+[url "ssh://${bound:forge-account:ssh_alias}/"]
+	insteadOf = ${bound:forge-account:https_base}

testdata/beside/mesh-catalog/modules/ssh-client/files/known_hosts

@@ -0,0 +1 @@
+${bound:forge-account:ssh_alias} ${bound:forge-account:host_key}