[js-contrib] Add dual-emit option for HTTP stable attributes in js-contrib instrumentations

[JamieDanielson]

trafficstars

Issues will be created in js-contrib repo. This is a placeholder for the milestone.

https://opentelemetry.io/docs/specs/semconv/attributes-registry/http/ https://opentelemetry.io/docs/specs/semconv/attributes-registry/network/

instrumentations using http:

• [ ] @opentelemetry/instrumentation-nestjs
  • SEMATTRS_HTTP_METHOD, SEMATTRS_HTTP_ROUTE, SEMATTRS_HTTP_URL
• [ ] @opentelemetry/instrumentation-aws sdk
  • SEMATTRS_HTTP_STATUS_CODE
• [x] @opentelemetry/instrumentation-hapi (https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2863)
  • SEMATTRS_HTTP_METHOD and SEMATTRS_HTTP_ROUTE
• [ ] @opentelemetry/instrumentation-document-loader
  • SEMATTRS_HTTP_URL and SEMATTRS_HTTP_USER_AGENT

instrumentations using net:

• @opentelemetry/instrumentation-net
  • SEMATTRS_NET_PEER_NAME, SEMATTRS_NET_PEER_PORT, SEMATTRS_NET_HOST_PORT, SEMATTRS_NET_TRANSPORT
  • SEMATTRS_NET_HOST_IP, SEMATTRS_NET_PEER_IP

net.peer.ip -> net.sock.peer.addr in 1.13.0 -> network.peer.address net.host.ip -> net.sock.host.addr in 1.13.0 -> network.local.address

Note: Right now this specifically excludes db instrumentations so they can be done in a separate run through, as the db semantic conventions have now become stable as well.