Migrate NestJs peer dependencies to 10/11 compat

[NikolaPeevski]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[x] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Currently the package supports the following peer dependencies as part of the NestJs ecosystem:

"@nestjs/common": "^8.0.0 || ^9.0.2",
"@nestjs/core": "^8.0.0 || ^9.0.2",
"@nestjs/platform-express": "^8.0.0 || ^9.0.2"

and uses version 8.4.7 as dev dependencies.

Expected behavior

Migrate the package so it supports latest and one version behind (11 and 10), preferably utilizing version 11 as dev deps.

Minimal reproduction of the problem with instructions

Locally:

1. Clone the repo
2. Bump package to 3.1.0
3. Use yalc with yalc publish to add to the local feed
4. Setup a basic nestJs project using nest new
5. Install manually via yalc add @nestjs/[email protected]
6. Do a simple rm -rf ./node_modules && npm i
7. Observe the wall of conflicts by npm resolution attempts

What is the motivation / use case for changing the behavior?

Let the users using latest or one version prior of the Nest ecosystem to use this package without a --force npm install each time.

Environment

Nest version: X.Y.Z
10/11+

For Tooling issues:

• Node version: N/A
• Platform: N/A

Others:
Refs:

• Dependency issue #313
• Update dependencies #326

CC: @manekinekko @kamilmysliwiec

[kamilmysliwiec]

Would you like to create a PR for this?

[NikolaPeevski]

@kamilmysliwiec Yes, please assign me to this issue, I'll log another one for the initial hurdle I started this series off haha, to migrate the Azure Storage to v11+ will ping you later for it.