feat(graphql): support explicit args type names

[xudongcc]

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?

• 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?

@ObjectType() and @InputType() support explicit GraphQL type names through @ObjectType(name, options?) and @InputType(name, options?), but @ArgsType() only accepts ArgsTypeOptions and always uses the TypeScript class name for metadata.

Issue Number: #4023

What is the new behavior?

@ArgsType() now supports the same explicit-name overload shape:

@ArgsType()
@ArgsType(options)
@ArgsType(name, options?)

The implementation follows the existing ObjectType and InputType decorator pattern, preserving ArgsTypeOptions such as registerIn and falling back to target.name when no explicit name is provided. The browser/react-native model shim accepts the same arguments.

Does this PR introduce a breaking change?

• Yes
• No

Other information

Verified with:

COREPACK_ENABLE_PROJECT_SPEC=0 corepack yarn workspace @nestjs/graphql test:e2e tests/decorators/register-in.decorator.spec.ts
COREPACK_ENABLE_PROJECT_SPEC=0 corepack yarn build
COREPACK_ENABLE_PROJECT_SPEC=0 corepack yarn lint
COREPACK_ENABLE_PROJECT_SPEC=0 corepack yarn format --check
git diff --check

[kamilmysliwiec]

could you target this #3973 branch?

[xudongcc]

could you target this #3973 branch?

@kamilmysliwiec Thanks! I've retargeted this PR to the v14.0.0 branch and rebased it. The conflict is resolved and CI is green now.