Remove non-generic instrumentations from defaults

[wpessers]

This PR reduces the amount of default instrumentations. These are the instrumentations that are initialized by default when a user does not set the OTEL_NODE_ENABLED_INSTRUMENTATIONS environment variable on their lambda function.

The current defaults include a lot of instrumentations that are not generic. e.g. the express instrumentation is only useful to users who use the express.js framework in their lambda, but is currently part of the defaults.

To start I have reduced the list of defaults to contain:

dns
http
net

Having http instrumentation seems like a sensible default, as it is used under the hood by many other packages.

What concerns dns and net instrumentation, I can see a good case for removing those from the defaults as well.

• dns: Do we need dns lookup etc spans by default?
• net: Do we need tcp level spans by default?
  I'm personally leaning towards removing these from defaults as well. Any input here is appreciated!

fixes #1735

[pragmaticivan]

I'm honestly content with this list:

dns
http
net

While not extremely useful, DNS and Net might be relevant for some people and are generic enough that they might be worth keeping as default.

[pragmaticivan]

@serkan-ozal @rapphil What are your thoughts on that one? Maybe something to bundle with Otel 2.0 for a major version release?

[serkan-ozal]

Yeah, let's keep this PR for the major release.

[tylerbenson]

Are we are intending to "major release" the lambda layers? I'm fine if we decide to just stay at 0.x.

[pragmaticivan]

Are we are intending to "major release" the lambda layers? I'm fine if we decide to just stay at 0.x.

Not sure if we can do that on the AWS level (tag) but removing default values is usually a major change because there might be dashboards using that set of instrumentation that will stop working correctly.

[pragmaticivan]

@tylerbenson @serkan-ozal have we reached consensus on what's the next step to get this one sorted?