feat(instrumentation-mongoose): Support v7 and v8

[onurtemizkan]

Resolves: #1606

Which problem is this PR solving?

Related: getsentry/sentry-javascript#11499

• This PR adds support for Mongoose versions 7 and 8 to the instrumentation.

Short description of the changes

Mongoose 7

• The instrumentation already supports async Mongoose operations.
• Moved tests using callbacks into a separate Mongoose v5/v6 test file
• Skipped instrumentation for deprecated remove Mongoose Docs

Mongoose 8

• Skipped instrumentation for deprecated count Mongoose Docs
• Skipped instrumentation for deprecated findOneAndRemove Mongoose Docs

The current set of tests is passing without any issues, except findOneAndUpdate, which starts to create only one span, starting from version 7. I separated that test for v7/v8.

To avoid separating the package because of type mismatches, I have added a few // @ts-expect-errors inside tests with their reasons.

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.56%. Comparing base (dfb2dff) to head (a373fc8).
Report is 209 commits behind head on main.

Files	Patch %	Lines
...gins/node/instrumentation-mongoose/src/mongoose.ts	94.11%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2353      +/-   ##
==========================================
- Coverage   90.97%   90.56%   -0.42%     
==========================================
  Files         146      157      +11     
  Lines        7492     7631     +139     
  Branches     1502     1574      +72     
==========================================
+ Hits         6816     6911      +95     
- Misses        676      720      +44     

Files	Coverage Δ
...gins/node/instrumentation-mongoose/src/mongoose.ts	98.43% <94.11%> (ø)

... and 74 files with indirect coverage changes

[trentm]

@onurtemizkan I haven't reviewed this PR, yet. A side issue: I notice that you are force-pushing. If you are able, please don't force-push to a PR branch, at least not after there have been any reviews on it. It makes it harder to do subsequent re-reviews because it isn't clear what has changed from a previous commit.

[onurtemizkan]

Thanks for looking into this @trentm, and yes I'll be careful not to force-push on reviewed code. FWIW these last couple were rebases on main.

[trentm]

Thanks for the PR. This looks good, modulo a couple suggestions below.

Please also apply this change to the README.md:

diff --git a/plugins/node/instrumentation-mongoose/README.md b/plugins/node/instrumentation-mongoose/README.md
index c5500b14..31a19b4e 100644
--- a/plugins/node/instrumentation-mongoose/README.md
+++ b/plugins/node/instrumentation-mongoose/README.md
@@ -17,7 +17,7 @@ npm install --save @opentelemetry/instrumentation-mongoose

 ## Supported Versions

-- [`mongoose`](https://www.npmjs.com/package/mongoose) versions `>=5.9.7 <7`
+- [`mongoose`](https://www.npmjs.com/package/mongoose) versions `>=5.9.7 <9`

 ## Usage