fix(NODE-5791): type error with $addToSet in bulkWrite

[alenakhineika]

Description

The update methods for Collection and BulkWrite with $addToSet should not show a type error for collections with shema, collections extended from the Document/any type, and fields of any type.

What is changing?

• The type of update in Collection.UpdateOneModel/Collection.UpdateManyModel/BulkWrite.updateOne/BulkWrite.updateMany becomes UpdateFilter<TSchema> | Document[].
• The SetFields type helper skips validation for fields of any type (provided by custom interface or index signatures).

Is there new documentation needed for these changes?

None

What is the motivation for this change?

NODE-5647
NODE-4664

Release Highlight

The type error with $addToSet in bulkWrite was fixed

Previously the following code sample would show a type error:

interface IndexSingatureTestDocument extends Document {
    readonly myId: number;
    readonly mySet: number[];
  }
const indexSingatureCollection = undefined as unknown as Collection<IndexSingatureTestDocument>;
indexSingatureCollection.bulkWrite([
  {
    updateOne: {
      filter: { myId: 0 },
      update: {
        $addToSet: { mySet: 0 } // The type error! Type 'number' is not assignable to type 'never'.
      }
    }
  }
]);

It happened because the driver's Document type falls back to any, and internally we could not distinguish whether or not this assignment was intentional and should be allowed.

After this change, users can extend their types from Document/any, or use properties of any type and we skip the $addToSet validation in those cases.

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