perf(NODE-5875): use builtin native crypto

[nbbeeken]

Description

What is changing?

Is there new documentation needed for these changes?

What is the motivation for this change?

Increase decryption performance

BenchmarkRunner is using libmongocryptVersion=1.10.0, warmupSecs=2, testInSecs=57
samples taken:  2
samples taken:  57
Decrypting 1500 fields median ops/sec : 415

Release Highlight

Improve performance by using bundled native crypto APIs

Previously the bindings would rely on the cryptoCallbacks option which was an object with javascript functions corresponding to the cipher algorithms used by libmongocrypt. Since supported versions of Node.js always bundle OpenSSL we can rely on the native APIs being available directly to libmongocrypt. This improves decryption performance ~x5.5 since data does not need to pass between native and javascript layers as frequently.

The bindings will check for the existence of OpenSSL APIs and will fallback to using the cryptoCallbacks if they are not present. This requires building with a version of libmongocrypt that does not link with OpenSSL.

Double check the following

• Ran npm run check:lint script
• 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

[nbbeeken]

After a tech chat discussion the changes here is not what we want. We will continue to compile with nocrypto but adjust to create callbacks in C++ instead of from JS.

[nbbeeken]

Preferred change: #25