fix(schematics): resolve built-in collection by path

[yudin-s]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

When @nestjs/cli is installed globally with pnpm 11, nest new can fail before scaffolding because the spawned Angular schematics CLI cannot resolve the built-in @nestjs/schematics collection from pnpm's global store layout.

Issue Number: Fixes #3471

What is the new behavior?

NestCollection resolves the installed @nestjs/schematics package metadata and invokes schematics through the package's concrete collection file path. The collection path is quoted so installs under paths containing spaces still work.

Because schematics-cli treats collection file paths as local collections, the CLI also passes --no-debug to avoid enabling debug/dry-run defaults for normal nest new and nest generate commands.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Local validation:

npm test -- --runTestsByPath test/lib/schematics/nest.collection.spec.ts
npm run build
npm exec -- prettier --check lib/schematics/nest.collection.ts test/lib/schematics/nest.collection.spec.ts
git diff --check
npm pack --pack-destination /tmp/nest-3471-pr-pack
# Install the packed CLI with pnpm 11 in an isolated global home, then:
nest new pr-example --skip-install --skip-git -p pnpm