feat(NODE-3740): Implement root and top level key utf-8 validation settings for BSON

[gjchong25]

Description

Adds a new validation option in DeserializeOptions that allows all or a specific subset of top-level keys in a document to be excluded from strict utf-8 validation and instead applies the replacement character behavior. Tests are added to make sure that both global and specific-key subsets can have utf8 validation enabled and disabled.

What is the motivation for this change?

Default behavior is to have strict utf-8 validation (an error will be thrown if invalid utf8 is detected). This change gives users the ability to opt into character replacement behavior instead of strict utf-8 validation.

Double check the following

• Ran npm run lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[nbbeeken]

Some initial feedback!

Side note: can you run npm install and push the package-lock changes, looks like its not sync-ed up with main from the last release.

[nbbeeken]

whoops accidentally cleared my review state

[nbbeeken]

I'm going to try and investigate the strange rollup issue in CI tomorrow, but we can manually verify this works as expected in the browser if it comes to it.

[dariakp]

Still working on reviewing the rest of the code, but wanted to capture this small suggestion

[dariakp]

Finished reviewing the code, still need to double check the tests

[dariakp]

Just a couple of things left to clean up

[nbbeeken]

LGTM!!!