feat: integrate Vercube GraphQL adapter and decorators

[productdevbook]

• Added VercubeGraphQLAdapter for seamless integration with nitro-graphql core.
• Implemented decorators for defining GraphQL resolvers (Query, Mutation, Subscription, FieldResolver).
• Enhanced code generation capabilities with skipValidationSchemas option for non-Nitro frameworks.
• Introduced runtime-only exports to reduce bundle size for environments not requiring type generation.
• Updated pnpm workspace configuration with new dependencies and overrides.
• Refactored server type generation logic to improve plugin architecture and flexibility.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	59.35%	955 / 1609
🔵	Statements	59.37%	969 / 1632
🔵	Functions	54.8%	154 / 281
🔵	Branches	50.91%	584 / 1147

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
src/core/runtime.ts	0%	0%	0%	0%
src/core/codegen/server.ts	88.88%	66.66%	80%	88.88%	59, 128-130
src/vercube/adapter.ts	0%	0%	0%	0%	28-221
src/vercube/controller.ts	0%	0%	0%	0%
src/vercube/decorators.ts	0%	0%	0%	0%	31-151
src/vercube/plugin.ts	0%	0%	0%	0%	24-174
src/vercube/types.ts	0%	0%	0%	0%

Generated in workflow #350 for commit a6dc7f2 by the Vitest Coverage Report Action

[productdevbook]

@OskarLebuda playgrounds/vercube in pnpm nitro-graphql generate used. As far as I understand, there is no structure to connect the nitro-graphql CLI directly to the vercube cli system, so they have to do this in a second terminal.

[OskarLebuda]

@OskarLebuda playgrounds/vercube in pnpm nitro-graphql generate used. As far as I understand, there is no structure to connect the nitro-graphql CLI directly to the vercube cli system, so they have to do this in a second terminal.

So far there's no chance to connect to the vercube cli but I think we can make it possible. For now this should be running in separated terminal