feat(generate): accept type and crud options on the resource schematic

[yogeshwaran-c]

What kind of change does this PR introduce?

Bug-fix backport from master to v12.0.0, with added unit tests.

What is the current behavior?

The @nestjs/schematics resource generator defines --type and --crud options in its schema.json. On master the CLI registers and forwards them (see #3275, which closed #3229). On v12.0.0 neither flag is wired up, so:

nest g resource users --type rest --crud

exits with error: unknown option '--type' even though the schematic itself would consume both flags correctly.

What is the new behavior?

• Register --type [type] and --crud on the generate command
• Forward both into GenerateCommandContext and on to the schematic
• Only forward --crud when explicitly passed so users who never opted in aren't affected

After this PR:

nest g resource users --type rest --crud
# Generates src/users/{users.module.ts, users.controller.ts, users.service.ts, dto/, entities/}

Additional context

The original master PR noted "No automated tests were added because there are no existing e2e tests for generate resource." This PR adds a focused unit spec (test/actions/generate.action.spec.ts) covering the new option wiring end-to-end at the action layer — forwarded when set, omitted when undefined/false.

Files changed:

• commands/generate.command.ts — register --type / --crud, populate context
• commands/context/generate.context.ts — extend GenerateCommandContext
• actions/generate.action.ts — push type / crud schematic options
• test/actions/generate.action.spec.ts — new unit spec (6 cases)

Closes #3229 for the v12 line.

Test plan

• npm run build clean
• npx vitest run test/actions/generate.action.spec.ts — 6/6 pass
• Full npm test local: 488 pass, 5 fail — the 5 failures are the pre-existing Windows-only issues in tsconfig-paths.hook.spec.ts (tracked separately in test(hooks): normalize emit path separators for windows #3398)