Bump mongodb from 3.6.4 to 3.6.6 in /integration

[dependabot]

Bumps mongodb from 3.6.4 to 3.6.6.

Release notes

Sourced from mongodb's releases.

v3.6.6

The MongoDB Node.js team is pleased to announce version 3.6.6 of the driver

Release Highlights

This patch addresses a number of bugs listed below. Most notably, for client side encryption users upgrading to this version of the driver along with the new version of mongodb-client-encryption@1.2.3 will alleviate the potential deadlock case if your connection pool was fully utilized. There will now be an internal MongoClient that will be used for metadata look ups (e.g, listCollections) when the pool size is under certain constraints. The events generated from this client are forwarded to the client instance you initialize so it is possible to monitor all events.

Bug

• [NODE-2995] - Sharing a MongoClient for metadata lookup can lead to deadlock in drivers using automatic encryption
• [NODE-3050] - Infinite loop on Windows due to a bug in require_optional package
• [NODE-3120] - TypeError: Cannot read property 'roundTripTime' of undefined
• [NODE-3122] - Pipelining an upload stream of GridFSBucket never finishes on Node v14
• [NODE-3129] - Collection () .. .setReadPreference() not routing query to secondaries
• [NODE-3133] - autoEncryption produces serverHeartbeatFailed - with MongoError typemismatch

Improvement

• [NODE-3070] - Define error handling behavior of writeErrors and writeConcernError on Mongos

Documentation

• Reference: http://mongodb.github.io/node-mongodb-native/3.6
• API: http://mongodb.github.io/node-mongodb-native/3.6/api
• Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md

We invite you to try the driver immediately, and report any issues to the NODE project.

Thanks very much to all the community members who contributed to this release!

v3.6.5

The MongoDB Node.js team is pleased to announce version 3.6.5 of the driver!

Notable Fixes

In this patch there is a fix surrounding an issue some users were encountering in serverless environments when using the Unified Topology. If the nodejs process went unused for a great amount of time there was an intermittent issue that would cause startSession to fail, however, issuing a dummy read request would resolve the problem. The session support check is now done after server selection meaning the driver has the most up to date information about the MongoDB deployment before utilizing sessions. We encourage any user's that implemented workarounds to updated their driver and make use of this fix.

In addition, the previous release of our driver added a warning about an upcoming change in the v4 version of the driver about how users can specify their write concern options. We've updated the driver to use nodejs's process.emitWarning API in nearly all cases where the driver prints something out, as well as limit most warning messages to only be printed once.

Bug

• session support detection spec compliance (#2732) (9baec71)
• [NODE-3100] - startSession fails intermittently on servers that support sessions
• [NODE-3066] - Accessing non-existent property 'MongoError' of module exports inside circular dependency
• [NODE-3114] - Incorrect warning: Top-level use of w, wtimeout, j, and fsync is deprecated
• [NODE-3119] - Node 14.5.4, mongo 3.6.4 Circular warnings

Commits

• dfb03ad chore(release): 3.6.6
• 5a0d706 chore: reintroduce nodejs fermium testing (#2775)
• af49ba3 test(NODE-3070): Ensure that SDAM should ignore the writeErrors field (#2769)
• 312ffef fix(NODE-3109): prevent servername from being IP (#2763)
• 9256242 fix(NODE-2995): Add shared metadata MongoClient (#2760)
• 91ba19e fix: ensure cursor readPreference is applied to find operations (#2751)
• f2a4ff8 fix: no infinite loop on windows requiring optional deps
• 86bddf1 fix(csfle): ensure that monitoring connections are not encrypted (#2749)
• b94519b fix: ensure monitor has rtt pinger in when calculating rtt (#2757)
• c976a01 fix: always close gridfs upload stream on finish (#2758)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like mongodb is up-to-date now, so this is no longer needed.