feat: define server composition APIs

[leoafarias]

Summary

Introduce the definition-first server composition surface for the 1.0 preview. Applications can now use createServer(definition), custom integrations can use defineAuthAdapter(...), and auth bootstraps can contribute the resources, metadata, repository setup, and guard preference they own.

Changes

• Add the canonical createServer(definition) Nest entry-module facade.
• Add defineAuthAdapter(Adapter, options?) and deterministic bootstrap/default precedence.
• Move defineTypeOrmRepository into @concepta/rockets-repository-typeorm and remove the server subpath export.
• Align the Firebase adapter with direct synchronous options.
• Update package documentation and contract tests for the new public surface.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Refactoring
• Dependency update

Verification

• Build succeeds (corepack yarn build)
• Unit tests pass (61 files / 566 tests)
• E2E tests pass (31 files / 160 tests)
• Lint passes (yarn lint)

Checklist

• My code follows the existing patterns in the codebase
• I have updated relevant documentation
• I have added tests for new functionality

Compatibility

• Import defineTypeOrmRepository from @concepta/rockets-repository-typeorm; the former server export and /typeorm subpath are removed.
• Pass synchronous Firebase options directly to defineFirebaseAuth(...); asynchronous registration remains nested under forRootAsync.
• Public packages in this slice require Node.js 20 or newer.