fix(NODE-4103): respect BSON options when creating change streams

[kampofo]

Description

NODE-4103

What is changing?

The use of the filterOptions function was removed from the ChangeStreamCursor constructor.

Is there new documentation needed for these changes?

What is the motivation for this change?

The filterOptions function being used to filter the options passed into into the changeStreamCursor constructor, was filtering out the usage of any of the BSON options being passed in. So the function was removed to allow BSON options to be passed through successfully and any invalid options would be handled by the existing filtering already present.

When calling collection.watch with the BSON option
{ promoteLongs: false } and inserting a document { long: Long.fromNumber(0) } to a collection, the document emitted from the change stream should contain a long with the value 0. However, before the changes made, the filter options were preventing promoteLongs from being passed successfully, so the 0 inserted into the document would be of type number instead of an instance of Long as we specified in our options.

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>
• Changes are covered by tests
• New TODOs have a related JIRA ticket

[baileympearson]

Didn't mean to approve, I hit the wrong button