BREAKING CHANGE: use MongoDB node driver 6, drop support for rawResult option and findOneAndRemove()

[vkarpov15]

Summary

Use the latest commits to MongoDB Node driver's 6.0 branch to make sure Mongoose is compatible. 3 big changes:

1. No more rawResult option. This PR replaces rawResult with the includeResultMetadata option
2. Because of includeResultMetadata, we need to slightly restructure how orFail() works on findOneAndX(). Specifically, orFail() will now only error out when findOneAndX() doesn't return a document; previously, orFail() would also throw an error if upsert was set and a new document was upserted. With includeResultMetadata, detecting whether a document was upserted or not is no longer possible in general. However, I think this new approach makes more sense, or at least the TypeScript types make more sense, because TS types treat orFail() as making the query result non-nullable.
3. No more findOneAndRemove(). findOneAndRemove() was just a legacy wrapper around findOneAndDelete(), didn't even have its own middleware.

Examples

[hasezoey]

[email protected]:mongodb/node-mongodb-native.git#6.0

i think this PR should be marked as Draft(WIP), or is this intended to be merged like this into 8.0 until it comes out?

[AbdelrahmanHafez]

LGTM 👍

[hasezoey]

mongodb 6.0.0 requires nodejs 16.20.1 or higher

[hasezoey]

also from bson release notes:

Strings of length 12 can no longer make an ObjectId

tests:

     strings of length 12 are valid oids (gh-3365):

    custom casters:
CastError: Cast to ObjectId failed for value "12charstring" (type string) at path "myId" because of "BSONError"

  with inheritance:

Actual message: "Cast to ObjectId failed for value "12charstring" (type string) at path "test" because of "BSONError""

[hasezoey]

some minor markdown things

[vkarpov15]

@hasezoey fixed, can you please re-review?

[hasezoey]

looks good to me now.

i dont know if it is related to this PR, but some replica set tests are timing out, and one test somehow tried to run while drop is occuring

[vkarpov15]

@hasezoey I took a closer look and the test failures were indicative of a bug where we weren't passing session option to Document.prototype.deleteOne correctly, that's fixed now 👍