fix(NODE-6355): respect utf8 validation options when iterating cursors

[baileympearson]

Description

What is changing?

This PR ensures that any BSON utf8 validation options are provided to the deserializer when deserializing cursors.

Since on-demand BSON, cursors are deserialized on-demand. Documents are pulled out of the cursor using MongoDBResponse.get(), which returns an unparsed on-demand document. We then deserialize it using toObject().

However, although MongoDBResponse correctly applies BSON utf8 options to its deserialization logic, the on-demand document does not. This results in documents retrieved from a cursor being deserialized without the utf8 validation options.

Is there new documentation needed for these changes?

What is the motivation for this change?

Release Highlight

Fill in title or leave empty for no highlight

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]

The c3a9 condition is failing. Perhaps we need to be a bit more robust, searching for c3a9 after finding "insert" or "documents" so we know we're in the command.

[jia-zhen]

Please update and release it as soon as possible, as we are currently troubled by this issue.

[nbbeeken]

LGTM