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/index.ts

@@ -1,4 +1,19 @@
 export * from './postgres.js';
+export {
+    createGamePostgresConnector,
+    GamePrisma,
+    LogCategory,
+    LogScope,
+} from './gamePrisma.js';
+export type { GamePrismaClient } from './gamePrisma.js';
+export {
+    createGatewayPostgresConnector,
+    GatewayBuildStatus,
+    GatewayProfileStatus,
+    GatewayPrisma,
+    OAuthType,
+} from './gatewayPrisma.js';
+export type { GatewayPrismaClient } from './gatewayPrisma.js';
 export * from './db.js';
 export * from './logRepository.js';
 export * from './redis.js';