feat(frameworks): add NestJS support

[colbymchenry]

Closes #220.

Adds a nestjsResolver to the framework-resolution registry, following the established pattern (regex-over-comment-stripped-source, emitting route nodes + references edges to handler methods). NestJS is auto-detected from any @nestjs/* dependency in package.json (falling back to a scan of *.controller.ts / *.resolver.ts / *.gateway.ts).

Coverage — all four NestJS transport layers

Source	Route node	→ handler
@Controller('cats') + @Get(':id')	GET /cats/:id	findOne
@Controller('cats') + @Post()	POST /cats	create
@Resolver() + @Query(() => [Cat])	QUERY cats	cats
@Resolver() + @Mutation()	MUTATION addCat	addCat
@WebSocketGateway({namespace:'chat'}) + @SubscribeMessage('message')	WS chat:message	handleMessage

• HTTP: @Controller prefix joined with @Get/@Post/@Put/@Patch/@Delete/@Head/@Options/@All, including the common empty @Controller() / @Get() cases.
• GraphQL: @Query/@Mutation/@Subscription in @Resolver classes.
• Microservices: @MessagePattern/@EventPattern.
• WebSockets: @SubscribeMessage, prefixed with the gateway namespace.

Correctness details

• String-aware balanced-paren arg reader so GraphQL type thunks (@Query(() => [User])) aren't truncated at the inner ().
• Skips stacked decorators (@UseGuards, @HttpCode) when locating the handler method.
• Disambiguates @Query() — it's both a GraphQL method decorator and a REST parameter decorator; it only counts as GraphQL inside an @Resolver class.
• resolve() links injected *Service/*Controller/etc. references to their classes by Nest file-naming convention.

Tests / verification

• 62 framework tests pass (18 new: HTTP, GraphQL, microservice/WS, detect, resolve, commented-out regression).
• Full suite 661/661; tsc build clean.
• End-to-end index of a scratch NestJS project produced exactly the 5 routes above with resolved handler edges.

🤖 Generated with Claude Code