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/nextcloud/files/server.env

@@ -0,0 +1,14 @@
+POSTGRES_HOST=${bound:postgres-database:at}:${bound:postgres-database:port}
+POSTGRES_DB=${bound:postgres-database:as}
+POSTGRES_USER=${bound:postgres-database:as}
+POSTGRES_PASSWORD=${secret:postgres-database}
+NEXTCLOUD_ADMIN_USER=mesh-admin
+NEXTCLOUD_ADMIN_PASSWORD=${secret:admin}
+OBJECTSTORE_S3_HOST=${bound:s3-bucket:at}
+OBJECTSTORE_S3_PORT=${bound:s3-bucket:port}
+OBJECTSTORE_S3_BUCKET=${bound:s3-bucket:bucket}
+OBJECTSTORE_S3_KEY=${bound:s3-bucket:as}
+OBJECTSTORE_S3_SECRET=${secret:s3-bucket}
+OBJECTSTORE_S3_SSL=false
+OBJECTSTORE_S3_USEPATH_STYLE=true
+OBJECTSTORE_S3_REGION=${bound:s3-bucket:region}