feat(NODE-4878): Add remaining log configurable client options

[aditi-khare-mongoDB]

Description

mongodbLogComponentSeverities and mongodbLogMaxDocumentLength are now supported options in client options through the MongoClient constructor.

Users can now provide severity levels for loggable components through the MongoClient constructor, as well as max document length for their logs.

This feature is currently flagged as internal until Logging is released.

What is changing?

The user can provide component severities through clientOptions. If environment variables as well as client options are present, the client options will take precedence. If certain components are not specified in either, their severity level will default to the value of 'default.' If default is not specified, the severity level for all components will be 'off.'

These client options are only supported for the constructor, not for connection string.

Example:

 new MongoClient('mongodb://localhost:27017', 
     {  mongodbLogComponentSeverities:  {
          client: 'trace',
          topology: 'trace',
          default: 'warn',
        },
        mongodbLogMaxDocumentLength: 800
    }
);

Is there new documentation needed for these changes?

Yes, documentation for MongoClient options should be updated with updated logging information.

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

[W-A-James]

Can we also add a unit test for the mongodbLogMaxDocumentLength?

[W-A-James]

Current changes look good. Approval pending changing mongodbLogMaxDocumentLength to number and the surrounding code to treat it as an integer specifically from outcome of Slack thread.

[W-A-James]

LGTM. Failures are unrelated