bugfix(microservices): pass all arguments to request-scoped proxies

[Reasno]

Some microservices, such as gRPC, have more than one arguments in their
handler. Previously only the first argument, namely data itself, was passed
to the request-scoped proxies, stopping other arguments from propagating.

related to #2802

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?

Issue Number: #2802

What is the new behavior?

All arguments are passed into interceptors, pipes, etc.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 4243

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.03%) to 95.262%

---

Files with Coverage Reduction	New Missed Lines	%
packages/microservices/listeners-controller.ts	2	92.31%

Totals
Change from base Build 4230:	0.03%
Covered Lines:	3639
Relevant Lines:	3820

---

💛 - Coveralls

[Reasno]

The previous test case has a false positive.

In "createRequestScopedHandler when 'loadPerContext' throws" branch, the exception is not triggered by "loadPerContext", but triggered by undefined "coreModuleRef" in private method "registerRequestProvider".

Without attempting to fix two things in one PR, I stubbed the registerRequestProvider and left it untested, only covering what I intended to fix.

[kamilmysliwiec]

Thanks!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.