fix(NODE-6284): make sparsity and trimFactor optional

[baileympearson]

Description

What is changing?

Sparsity and trimFactor, two options for the QE Range, have been marked optional. All range v2 spec tests are syncced. CSFLE prose test 23 has been implemented.

Additionally, the crypto callbacks tests have been removed. The bindings now automatically load crypto callbacks from C++ with all compatible mongodb-client-encryption versions. This means we can no longer spy on or sinon stub the cypto callbacks, so these tests are broken.

Is there new documentation needed for these changes?

What is the motivation for this change?

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]

We're putting the release highlights of this change into: #4141 correct? Could you fill those out with the changes we're making here?

[baileympearson]

We're putting the release highlights of this change into: #4141 correct? Could you fill those out with the changes we're making here?

This is a fix to changes made in another PR that hasn't been released. There are no release notes for this - as far as users are concerned, this work never happened.

[nbbeeken]

This is a fix

Maybe I am overlooking something in this PR. Is it not the case that trimFactor?: Int32; is a new line of code? I do not see trimFactor in src on main.

I figure that we can still call this a "fix" PR but that this "feature" is a logical part of #4141 in the sense that it is "adding support for range v2"

[baileympearson]

This is a fix

Maybe I am overlooking something in this PR. Is it not the case that trimFactor?: Int32; is a new line of code? I do not see trimFactor in src on main.

I figure that we can still call this a "fix" PR but that this "feature" is a logical part of #4141 in the sense that it is "adding support for range v2"

I guess that was an oversight. The full feature will be documented in #4190 when the time comes.

[nbbeeken]

FYI, there's a lint error in the test file.