feat(common): disallow usage of inject on class and value providers at type level

[micalevisk]

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?

Issue Number: closes #9357

What is the new behavior?

At build time, we can no longer have the option inject when writing a class or value providers

The TS error would be like this:

Type '{ provide: string; useValue: number; inject: never[]; }' is not assignable to type 'Provider<any>'.
  Object literal may only specify known properties, and 'useValue' does not exist in type 'FactoryProvider<any>'.

Does this PR introduce a breaking change?

• Yes
• No

This will break the build step of projects that are using the inject value when defining a class or a value provider even tho this option does nothing on these providers.

[jmcdo29]

Looks go to me. I think we'll have to wait for v9 so that we don't break anyone's build until the major bump

[coveralls]

Pull Request Test Coverage Report for Build a702be58-22bb-4c44-af07-7c0fba684d21

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.001%) to 94.119%

---

Totals
Change from base Build f4e63af7-2696-4bb6-ba31-785c7b9652df:	-0.001%
Covered Lines:	5761
Relevant Lines:	6121

---

💛 - Coveralls