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

@@ -0,0 +1,18 @@
+# Next.js listens on the address HOSTNAME names, and docker sets HOSTNAME to the container's id,
+# so studio answered only on its network address while its image's health check asks localhost:
+# unhealthy for ever while working. Every address, as the upstream compose file has it.
+HOSTNAME=::
+STUDIO_PG_META_URL=http://supabase-meta:8080
+POSTGRES_PASSWORD=${secret:postgres}
+DEFAULT_ORGANIZATION_NAME=Default Organization
+DEFAULT_PROJECT_NAME=Default Project
+OPENAI_API_KEY=${secret:openai}
+SUPABASE_URL=http://supabase-kong:8000
+SUPABASE_PUBLIC_URL=https://${bound:route:name}
+SUPABASE_ANON_KEY=${secret:anon-key}
+SUPABASE_SERVICE_KEY=${secret:service-role-key}
+AUTH_JWT_SECRET=${secret:jwt}
+LOGFLARE_API_KEY=${secret:logflare}
+LOGFLARE_URL=http://supabase-analytics:4000
+NEXT_PUBLIC_ENABLE_LOGS=true
+NEXT_ANALYTICS_BACKEND_PROVIDER=postgres