fix(graphql): Backport metadata storage refactor bug fix

[jhpierce]

This PR backports a fix from v11.4.0 to v10.

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?

#2360 (comment)

Issue Number: 2360

What is the new behavior?

Fields resolver works correctly.

Does this PR introduce a breaking change?

• Yes
• No

Other information

Please advise if this PR is not set up correctly for backporting. Thank you!

[rezoled]

Looks fine to me, @kamilmysliwiec i don’t know what’s your policy on back-porting bug fixes.

[jhpierce]

@kamilmysliwiec friendly bump, thank you!

[jhpierce]

@kamilmysliwiec - We're running a pretty big codebase with a lot of moving parts. Moving to graphql 16 isn't really a tenable option for us, and this bug is preventing us from upgrading to >= 10.0.19. Unfortunately, we also can't update to <= 10.0.16, due to this bug. For some other reason, the handful of in-between versions wouldn't work either, and so we're a bit stuck but are pretty excited about leveraging some new features of v11 and staying up to date!

We'd really appreciate some help here. Thank you!

[kamilmysliwiec]

Fixed in 10.2.1