build(deps): COMPASS-4095: bump mongodb from 3.4.1 to 3.5.2

[dependabot-preview]

Bumps mongodb from 3.4.1 to 3.5.2.

Release notes

Sourced from mongodb's releases.

v3.5.2

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

Release Highlights

This patch release corrects a regression introduced in the 4.2 timeframe which would effectively disable retryable operations for connection to MongoDB 4.2+. Additionally, the server selection loop has been converted to a queue of callbacks to improve readability, as well as performance in certain scenarios.

Release Notes

Bug

• [NODE-2408] - retryWrites seems not to work as expected in failover test

Improvement

• [NODE-2398] - Use a queue for server selection

v3.5.1

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

Release Highlights

This patch release fixes a few regressions introduced with new connection pool, primarily around the ability to use custom TLS certificates.

Release Notes

Bug

• [NODE-2372] - db.findOne does not respect client setting bufferMaxEntries
• [NODE-2401] - "readPreference.equals is not a function" exception thrown within executeWithServerSelection
• [NODE-2424] - CMAP connection pool fails to create connection using SSL / TLS

v3.5.0

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

Release Highlights

... (truncated)

Commits

• 82b02bb chore(release): 3.5.2
• 75f445b refactor(topology): use a wait queue for server selection
• 0f4ab38 fix: properly handle err messages in MongoDB 2.6 servers
• 57f158f fix(topology): always emit SDAM unrecoverable errors
• d0bfd8a chore(release): 3.5.1
• 9169203 test: skip test that uses mongofiles for flakiness
• 667b34c test: fix failure to return promise in CSFLE prose test
• c8d182e fix(uri_parser): TLS uri variants imply ssl=true
• f8bdb8d fix(connect): listen to secureConnect for tls connections
• d13b153 fix(cmap): error wait queue members on failed connection creation
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[imlucas]

Travis failure:

  1) connection model connector
       local
         ssh tunnel failures
           should close ssh tunnel if the connection fails:
      Uncaught AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
  assert.ok(/ECONNREFUSED/.test(err.reason))

[imlucas]

err.reason was a string before. As of 3.5.0, looks like NODE-2397 changed it to

We will now surface the first encountered error in the set of known server descriptions as the primary error message for a
timeout error. The reason field for server selection errors
will now include the TopologyDescription for better traceability