feat(NODE-4796)!: remove addUser and collection.stats APIs

[nbbeeken]

Description

What is changing?

Removing deprecations

mongodb-js/nodejs-mongodb-legacy#22

Is there new documentation needed for these changes?

What is the motivation for this change?

Release Highlight

db.addUser() and admin.addUser() removed

The deprecate addUser APIs have been removed. The driver maintains support across many server versions and the createUser command has support for different features based on the server's version, since applications can generally write code to work against a uniform and perhaps more modern server the path forward is for applications to send the createUser command directly.

The associated options interface with this API has also been removed: AddUserOptions.

See createUser documentation: https://www.mongodb.com/docs/manual/reference/command/createUser/

const db = client.db('admin');
// Example addUser usage
await db.addUser(
  'myUsername', 
  'myPassword', 
  { roles: [ { role: 'readWrite', db: 'mflix' } ] }
);
// Example equivalent command usage
await db.command({ 
  createUser: 'myUsername', 
  pwd: 'myPassword', 
  roles: [ { role: 'readWrite', db: 'mflix' } ] 
});

collection.stats() removed

The collStats command is deprecated starting in server v6.2 so the driver is removing it's bespoke helper in this major release. The collStats command is still usable from manually running it via await db.command(). However, the recommended migration is to use the $collStats aggregation stage. You can find more information here: $collStats.

The associated interfaces with this API have also been removed: CollStatsOptions and WiredTigerData.

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]

I didn't flag all of them, but can we update the tests that got touched to use async syntax? Other than that, lgtm.

[W-A-James]

Is there any reason not to convert this test to use async syntax?