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/supabase/files/pooler-env.env

@@ -0,0 +1,14 @@
+PORT=4000
+POSTGRES_PORT=5432
+POSTGRES_DB=postgres
+POSTGRES_PASSWORD=${secret:postgres}
+DATABASE_URL=ecto://supabase_admin:${secret:postgres}@supabase-db:5432/_supabase
+CLUSTER_POSTGRES=true
+SECRET_KEY_BASE=${secret:key-base-a}${secret:key-base-b}
+VAULT_ENC_KEY=${secret:pooler-vault}
+API_JWT_SECRET=${secret:jwt}
+METRICS_JWT_SECRET=${secret:jwt}
+REGION=local
+ERL_AFLAGS=-proto_dist inet_tcp
+RELEASE_NODE=supavisor@127.0.0.1
+POOLER_POOL_MODE=transaction