Use Case

As a part of https://github.com/mongodb-js/mongodb-client-encryption/pull/25, our FLE bindings now contain C++ crypto callbacks that are automatically loaded into the FLE bindings. These are not available on all supported runtimes and configurations, so the existing crypto callbacks must continue to exist.

Now that there are C++ crypto callbacks in mongodb-client-encryption, it makes sense to move the JS crypto callbacks there as well so that both implementations are co-located (Anna's PR does this).

Now that all crypto callbacks are present in mongodb-client-encryption, we can remove the JS crypto callbacks file from the driver.

User Impact

• Depends. If we do this in a minor, users wouldn't be able to use `mongodb-client-encryption@6.0.0 with driver@6.9.0+ (or whatever version this ticket is released in). If we wait until the next major, there is none.

Dependencies

n/a.

Unknowns

• Can we make this change in a minor?

Acceptance Criteria

Implementation Requirements

• remove crypto_callbacks.ts and its associated tests from the driver.

Testing Requirements

n/a.

Documentation Requirements

n/a.

Follow Up Requirements

n/a.