feat(): Complexity options on Query and Mutation

[wSedlacek]

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
[x] 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: #1087

What is the new behavior?

@Query() and @Mutition() now have complexity options and pass them through to the already existing addResolverPropertyMetadata() method. No further changes are required to obtain the desired behavior

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[wSedlacek]

Purposed Documentation for this change.
nestjs/docs.nestjs.com#1416

[wSedlacek]

There does not appear to be any current testing for complexity, should I go ahead and add an e2e test for the feature for @ResolveFiled(), @Field(), @Query() and @Mutation()?

[jmcdo29]

I think the code looks fine, looks like it's just adding an option. E2E tests are always helpful if you have the time to add some.

[kamilmysliwiec]

Thanks @wSedlacek! This will be published as part of the next release