feat: Set up npm workspace structure for DBAL integration

Workspace Setup Complete:
- Added dbal/development to root package.json workspaces
- Added @metabuilder/dbal dependency to frontends/nextjs (file reference)
- Updated TypeScript paths in frontend to resolve via node_modules
- Installed workspace dependencies successfully

Structure Now In Place:
✅ dbal/development is registered as workspace
✅ @metabuilder/dbal dependency declared in frontend
✅ Path aliases configured for @/dbal resolution
✅ npm install works with all dependencies

Pre-existing DBAL Build Issues Found:
⚠️ src/core/foundation/types/types.generated missing
⚠️ CodeGen script (tsx ../shared/tools/codegen/gen_types.ts) failing
⚠️ exactOptionalPropertyTypes causing TypeScript errors in KV operations

These are pre-existing issues in DBAL code, not related to workspace setup.
Will need separate DBAL build fix task.

For now, workspace structure is ready for when DBAL build is fixed.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

dbal/development/src/seeds/index.ts

@@ -7,8 +7,8 @@
  * DBAL only manages the loading and application of that seed data.
  *
  * Seed data hierarchy:
- * 1. /seed/database/ - Base system bootstrap data (YAML format)
- * 2. packages/*/seed/metadata.json - Package-specific seed data
+ * 1. /seed/database - Base system bootstrap data (YAML format)
+ * 2. packages/[packageId]/seed/metadata.json - Package-specific seed data
  */
 
 import type { DBALClient } from '../core/client'