feat(common): introduce intrinsic exception

[kamilmysliwiec]

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: Tiny enhancement

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Base exception filters won't auto-log intrinsic errors. So far, this has been the default behavior only for HttpException errors

Does this PR introduce a breaking change?

• Yes
• No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 0437aad1-7980-44fc-9973-959c535010f9

Details

• 8 of 8 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.004%) to 90.109%

---

Totals
Change from base Build e0bf29f0-9145-4934-8bf2-9c17fbcadc0d:	0.004%
Covered Lines:	6969
Relevant Lines:	7734

---

💛 - Coveralls

[iamolegga]

Wondering if it's required to do like so: https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-2.html#support-for-newtarget

[kamilmysliwiec]

Been trying to mimic what we had so far for the HttpException