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/invoicing/files/api.env

@@ -0,0 +1,9 @@
+NODE_ENV=production
+PORT=9000
+MONGO_URL=mongodb://${bound:mongodb-database:as}:${secret:mongodb-database}@${bound:mongodb-database:at}:${bound:mongodb-database:port}/${bound:mongodb-database:as}?authSource=${bound:mongodb-database:as}
+MONGO_DB=${bound:mongodb-database:as}
+MINIO_BUCKET=${bound:s3-bucket:bucket}
+MINIO_ENDPOINT=${bound:s3-bucket:at}
+MINIO_PORT=${bound:s3-bucket:port}
+MINIO_ACCESSKEY=${bound:s3-bucket:as}
+MINIO_SECRET=${secret:s3-bucket}