build(express): upgrade to express 4.2.1

[ezintz]

fixes vulnerabilites with cookie and path-to-regexp.

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: fixes security vulnerabilities coming from the express package, which has already updated dependencies

What is the current behavior?

Currently security scanners like Anchore or Trivy are reporting vulnerabilities from express for certain packages. Please see

• GHSA-pxg6-pf52-xh8x
• GHSA-9wv6-86v2-598j

What is the new behavior?

Security scanners will not report vulnerabilities for the installed express package anymore.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 85c24b08-dacd-4f9a-9550-fa7cfadfb80b

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 92.213%

---

Totals
Change from base Build 9327011d-4e25-476d-80b9-dcb00dcd9e2d:	0.0%
Covered Lines:	6750
Relevant Lines:	7320

---

💛 - Coveralls

[Tony133]

The title of the PR should be corrected to build(express): upgrade to express 4.21.1, to specify better 😉, the strange thing is who knows why the dependabot or renovate does not automatically generate these corrections of security ? 🤔

[kamilmysliwiec]

LGTM