feat: add database schema support for gateway and game profiles

- Introduced `dbSchema` configuration option in GatewayApiConfig and GatewayOrchestratorConfig.
- Implemented schema resolution logic in environment configuration functions.
- Updated context and orchestrator factory to use GatewayPrismaClient instead of PrismaClient.
- Refactored orchestrator server and profile repository to accommodate new database schema handling.
- Created separate Prisma schemas for game and gateway in the infra package.
- Enhanced Postgres connector to support schema overrides in database URLs.
- Updated documentation to reflect changes in database schema handling.
- Added new Prisma generation and database push scripts for game and gateway schemas.

packages/infra/src/gatewayPrisma.ts

@@ -0,0 +1,19 @@
+import { PrismaClient as GatewayPrismaClient } from '../prisma/generated/gateway/index.js';
+export {
+    GatewayBuildStatus,
+    GatewayProfileStatus,
+    OAuthType,
+    Prisma as GatewayPrisma,
+} from '../prisma/generated/gateway/index.js';
+export type { PrismaClient as GatewayPrismaClient } from '../prisma/generated/gateway/index.js';
+
+import type { PostgresConfig, PostgresConnector } from './postgres.js';
+import { createPostgresConnector } from './postgres.js';
+
+export const createGatewayPostgresConnector = (
+    config: PostgresConfig
+): PostgresConnector<GatewayPrismaClient> =>
+    createPostgresConnector(
+        config,
+        (options) => new GatewayPrismaClient(options)
+    );