feat(NODE-5287): deprecate ssl options

[durran]

Description

Deprecates duplicate SSL options in favour of spec compliant TLS options.

What is changing?

Deprecates:

• sslCA
• sslCRL
• sslCert
• sslKey
• sslPass
• sslValidate
• tlsCertificateFile

Is there new documentation needed for these changes?

None

What is the motivation for this change?

NODE-5287

Legacy SSL options deprecated

In an effort to simplify TLS setup and use with the driver we're paring down the number of custom options to the ones that are common to all drivers. This should reduce inadvertent misconfiguration due to conflicting options.

The legacy "ssl-" options have been deprecated, each has a corresponding "tls-" option listed in the table below (except for sslCRL, you may directly use the Node.js crl option instead). tlsCertificateFile has also been deprecated, please use tlsCertificateKeyFile or pass the cert directly to the MongoClient constructor.

In addition to the common driver options, the Node.js driver also passes through Node.js TLS options provided on the MongoClient to Node.js' tls.connect API, which may be convenient to reuse with other Node.js APIs.

Node.js native option	MongoDB driver option name	legacy option name	driver option type
ca	tlsCAFile	sslCA	string
crl	N/A	sslCRL	string
cert	tlsCertificateKeyFile	sslCert	string
key	tlsCertificateKeyFile	sslKey	string
passphrase	tlsCertificateKeyFilePassword	sslPass	string
rejectUnauthorized	tlsAllowInvalidCertificates	sslValidate	boolean

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