Take the catalogue's composition rules into the node-engine

ADR 0593 §7: the composer with its refusals leaves mesh-sdk, so mesh-sdk
carries no composition rule. The catalogue functions only the
node-engine's composition reaches (Resolve, Resolution's Compose,
Declaration, DataItems, LeftOut, Rules and the rest, the settings,
placeholder and template refusals, the rendering helpers) are copied
with their tests into internal/compose/resolution; a method of a
mesh-sdk shape becomes a function taking it first. The composition
calls its own copies, and the captured catalogue its tests read lives
here now, shared by mesh-compose's tests.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

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

@@ -0,0 +1,52 @@
+{
+  "module": "openrazer",
+  "version": "1",
+  "capabilities": [
+    "package-manager"
+  ],
+  "tools": [
+    "openrazer_status",
+    "openrazer_restart",
+    "openrazer_check"
+  ],
+  "resources": [
+    {
+      "id": "driver",
+      "type": "package",
+      "package": "openrazer-driver-dkms"
+    },
+    {
+      "id": "daemon",
+      "type": "package",
+      "package": "openrazer-daemon"
+    },
+    {
+      "id": "library",
+      "type": "package",
+      "package": "python-openrazer"
+    },
+    {
+      "id": "account",
+      "type": "user",
+      "name": "${machine:account}",
+      "groups": [
+        "openrazer"
+      ]
+    }
+  ],
+  "build": {
+    "artifacts": [
+      {
+        "name": "tools",
+        "kind": "bundle",
+        "language": "go",
+        "system": "arch",
+        "from": "cmd/openrazer-tools",
+        "binary": "openrazer-tools",
+        "loads": [
+          "openrazer-tools"
+        ]
+      }
+    ]
+  }
+}