feat(NODE-5545): remove deprecated objects

[durran]

Description

Removes deprecated items or marks them internal where appropriate.

Summary of Changes

What is the motivation for this change?

NODE-5545

Release Highlight

Deprecated Types, Classes, and Options Have Been Removed

Includes:

GridFSFile.contentType
GridFSFile.aliases
GridFSBucketWriteStreamOptions.contentType
GridFSBucketWriteStreamOptions.aliases
CloseOptions
ResumeOptions
MongoClientOptions.useNewUrlParser
MongoClientOptions.useUnifiedTopology
CreateCollectionOptions.autoIndexId
FindOptions<TSchema> // Now no generic type.
ClientMetadataOptions
FindOneOptions.batchSize
FindOneOptions.limit
FindOneOptions.noCursorTimeout
ReadPreference.minWireVersion
ServerCapabilities
CommandOperationOptions.retryWrites // is a global option on the MongoClient
ClientSession.transaction
Transaction
CancellationToken // Use AbortSignal instead.

Double check the following

• Lint is passing (npm run check:lint)
• 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

[baileympearson]

Just a few minor comments!

[baileympearson]

Probably fine because I don't expect users to actually be using this type. But want to confirm we're okay making this field internal, even though it isn't deprecated?

[dariakp]

it's kind of annoying that this is a public type at all - best I can tell it's all for the supported tls options list; I wonder if we could invert our types for the next major where this interface can be private, composed of the public options plus whatever else we need internally...

I think we should make a note of this so that we can consider releasing a minor version with the deprecation before the major, but I don't think we need to commit to actually doing it for just this one thing

[durran]

I've updated this to deprecated now with a note on what to use instead.

[dariakp]

I meant make a note outside this PR (e.g. a follow up ticket that we can consider doing or not when we get closer to release time)... we should remove it in this PR.

[durran]

@baileympearson #4704 (comment)

I've updated the GridFS tests to latest and skipped the new ones.

[dariakp]

it's kind of annoying that this is a public type at all - best I can tell it's all for the supported tls options list; I wonder if we could invert our types for the next major where this interface can be private, composed of the public options plus whatever else we need internally...

I think we should make a note of this so that we can consider releasing a minor version with the deprecation before the major, but I don't think we need to commit to actually doing it for just this one thing

[dariakp]

I think this can just be deleted - the comment above says the intention is to make sure we don't remove the generic - we are now intentionally removing the generic

[durran]

Removed.