fix(NODE-5102): fix listDatabases nameOnly setting is sent as NaN

[redixhumayun]

Description

Fixes the issue described in NODE-5102 where nameOnly was being coerced into NaN using the Number constructor.

What is changing?

Now, the nameOnly property is coerced to a boolean following the example laid out by listCollections. Accompanying unit tests have also been added.

Is there new documentation needed for these changes?

No

What is the motivation for this change?

Fixes NODE-5102

Release Highlight

listDatabases nameOnly option bug fix

The listDatabases API exposes the nameOnly option which allows you to limit its output to only the names of the databases on a given mongoDB deployment:

db.admin().listDatabases({ nameOnly: true });
// [
//   { name: 'local' },
//   { name: 'movies' },
//   ...
// ]

Prior to this fix, the option was not being set properly on the command, so the output was always given in full.

Thanks to @redixhumayun for submitting this fix!

See #3742 for details.

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]

Hi @redixhumayun, thanks so much for this PR. I have left some specific comments on the files below. In addition to the unit tests you have written, before we can approve this change, we would need to have integration tests that would test this behaviour against a mongod instance. It would be good to create a new file for these in test/integration/enumerate_databases.test.ts.

Please see the running tests locally section section of our test readme for details on how to get integration tests running locally.

For an example of how to write an integration test in this repo, please see the findAndModify tests.

[W-A-James]

@redixhumayun We do want to merge this change fairly soon, so we will take over the remaining code changes on this PR. Thanks again for your submission!