feat(NODE-7043, NODE-7217, NODE-6793)!: adopt mongodb-client-encryption v7

[baileympearson]

Description

Summary of Changes

This PR is a small feature branch containing the driver changes corresponding to breaking mongodb-client-encryption changes. It contains:

• Error wrapping for errors thrown from mongodb-client-encryption in MongoCryptError instances.
• Removal of enableMultipleCollInfo (it now defaults to 'enabled')
• Removes crypto callbacks from the driver

Warning

Do not merge this PR until all mongodb-client-encryption changes are completed, an alpha has been released, and this PR is updated to use the alpha.

Notes for Reviewers

The changes in mongodb-js/mongodb-client-encryption#102 must be released before CI passes fully. The custom dependency tests use the changes from my other PR and should be passing.

What is the motivation for this change?

Release Highlight

Release notes highlight

Double check the following

• Lint is passing (npm run check:lint)
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[evergreen-ci-prod]

There is an existing patch(es) for this commit SHA:

• Evergreen patch with PR

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.

[baileympearson]

superceded by #4694

[evergreen-ci-prod]

There is an existing patch(es) for this commit SHA:

• Evergreen patch with PR

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.

[dariakp]

I don't have a better place to leave a comment, but we wanted to remove the custom matcher isMongoCryptError from the unified spec runner