fix(graphql): add deprecationReason to ArgsOptions

[hayatekiribayashi]

The official document said that @Args option allowed deprecationReason, but it did not. GraphQL allows deprecation directives for arguments, so I made it allow deprecationReason.

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?

Issue Number: #3033

What is the new behavior?

I make changes to AuthorResolver of https://github.com/bodil-dev/nest-graphql-args-deprecated . Because, deprecated arguments required nullable or default value. (see https://spec.graphql.org/draft/#sec--deprecated)
And I add @ArgsType usage.

Then, @deprecated will be given properly.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[kamilmysliwiec]

Could you update tests too?

[hayatekiribayashi]

@kamilmysliwiec
Yes, but I want to know testing strategy in this project. Only a few tests exist now.
Should I write a integrative test for GraphQLSchemaBuilder? (e.g. expect to generate rigth schema from decorated class definition)
or, individual unit test for @Args and ArgsFactory? (e.g. expect to set deprecationReason to metadata/configMap)

[kamilmysliwiec]

e2e test that confirms that auto-generated schema contains deprecation messages added through this attribute