feat: Add tracing channel support

[logaretm]

This PR explores adding tracing channels to enable agnostic observability for users and APMs alike without having to resort to monkey patching or module patchers.

Unlike the original proposal in #16105, I realized that one channel is cleaner and allows for creating all the needed span descriptions that currently exist in the OTEL instrumentation. This keeps the changes small and managable.

Implementation

So a singlemongoose:query channel that emits the following payload:

Field	Type	Description
operation	string	The operation name (e.g. find, updateOne, aggregate)
collection	string	MongoDB collection name
database	string	Database name
serverAddress	string	DB host
serverPort	number	DB port
args	Record<string, any>	Operation-specific arguments

I also exported the types for use by consumers.

Example Consumer

const dc = require('node:diagnostics_channel');

const channel = dc.tracingChannel('mongoose:query');

channel.subscribe({
  start({ operation, collection, database, serverAddress, serverPort, args }) {
    console.log('[query:start]', operation, collection, args);
  },
  asyncEnd({ operation, collection, result }) {
    console.log('[query:end]', operation, collection);
  },
  error({ operation, collection, error }) {
    console.error('[query:error]', operation, collection, error);
  }
});

this is what it looks like after consuming the events in an APM, which is inline with current instrumentations today.

closes #16105