feat(NODE-5639): keep executing context on queued commands

[david-luna]

Description

Implementation for https://jira.mongodb.org/browse/NODE-5639

Make use of AsyncResource.bind API to bind the current execution context of WaitQueueMember callback.

The change proposed will make callbacks to have the same context they where created. Useful if the consumer of the package is using AsyncLocalStorage to keep state.

One use case is APM agents. They make use of these APIs to keep context between callbacks and async calls.

What is changing?

Bind the current execution context to WaitQueueMember callback property.

Is there new documentation needed for these changes?

No

What is the motivation for this change?

Get span hierarchy right when mongodb driver is instrumented by an APM agent like Opentelemetry, Elastic, DataDog...

Release Highlight

Fill in title or leave empty for no highlight

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

[baileympearson]

This PR should be unnecessary now that the driver uses async-await internally.