feat(instrumentation-console): Add console intrumentation

[hectorhdzg]

Adding console instrumentation, following similar configurations and functionality in other Log instrumentations in this project like Bunyan, Winston and Pino

#3444

[JacksonWeber]

Looks like we're ensuring that console.trace() contains the message field here, but trace should also print a stack trace. We should ensure that the stack is also captured with this instrumentation.

[JacksonWeber]

Minor comment, but overall LGTM.

[pichlermarc]

Might be worth syncing with the browser SIG, they also currently have a PR open, but they'll likely integrate it into their single instrumentation package:
open-telemetry/opentelemetry-browser#98

[hectorhdzg]

@pichlermarc this is specific to Node.js console not browser, we should ensure there are no name conflicts and customer confusion, I can rename this package to @opentelemetry/instrumentation-console-nodejs or something like that, what you think?

[hectorhdzg]

This is not using require/import in the middle, that would work if people import manually the console from their code, that is usually not the case and people rely on global console.

[trentm]

can rename this package to @opentelemetry/instrumentation-console-nodejs or something like that, what you think?

+1. FWIW, we've used "-node" suffix in a couple cases:

% ls ~/src/opentelemetry-js-contrib/packages | rg node
auto-instrumentations-node
instrumentation-runtime-node

So perhaps instrumentation-console-node.

[pichlermarc]

can rename this package to @opentelemetry/instrumentation-console-nodejs or something like that, what you think?

+1. FWIW, we've used "-node" suffix in a couple cases:

% ls ~/src/opentelemetry-js-contrib/packages | rg node
auto-instrumentations-node
instrumentation-runtime-node

So perhaps instrumentation-console-node.

-node suffix sounds good to me. 👍