feat(instrumentation-undici): add undici and fetch instrumentations

[david-luna]

Which problem is this PR solving?

This PR adds a new instrumentation that subscribes to the diagnostic channels used by undici pacakge. The instrumentation will get traces from:

• undici package
• global fetch API since this is implemented using undici internally and publishes the same messages on the same diagnostic channels.

Code was donated by @djMax from https://github.com/gas-buddy/service/blob/main/src/telemetry/fetchInstrumentation.ts

NOTE: the PR is marked as draft since there are some todos (to be discussed in comments)

• wether to have a configuration similar to the HTTP one
• make sure is not mixed with HttpInstrumentation
• differentiate between a req made with fetch or using undici explicitly? decided it's not necessary (HTTP instrumentation doesn't for http livs like axios, got,...)
• adjust node versions supported

Fixes #4333

Short description of the changes

• add a new package with an instrumentation for undici

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

By unit tests.

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[david-luna]

1st discussion point

wether to have a configuration similar to the HTTP one

IMHO I think we should have the configuration that applies to fetch & undici which is the one concerning outgoing requests. You can check the options in https://github.com/open-telemetry/opentelemetry-js/blob/main/experimental/packages/opentelemetry-instrumentation-http/README.md?plain=1#L51

[david-luna]

about 3rd point

differentiate between a req made with fetch or using undici explicitly?

I think it could be misleading if a customer is using fetch but the traces extracted refer only to undici. We may check if there is info on the request that could help us to figure it out or otherwise instrument undici's dispatch method to add this info on the request.

[codecov]

Codecov Report

Merging #4393 (092b9c1) into main (f4b681d) will decrease coverage by 1.87%.
Report is 37 commits behind head on main.
The diff coverage is n/a.

❗ Current head 092b9c1 differs from pull request most recent head db97899. Consider uploading reports for the commit db97899 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4393      +/-   ##
==========================================
- Coverage   92.22%   90.36%   -1.87%     
==========================================
  Files         333      163     -170     
  Lines        9459     3799    -5660     
  Branches     2009      845    -1164     
==========================================
- Hits         8724     3433    -5291     
+ Misses        735      366     -369     

see 177 files with indirect coverage changes

[louislatreille-cb]

@david-luna Seems like you have done a lot of work so far!

I've just started using OpenTelemetry (which is awesome) and stumbled upon this issue in our project: #4247. I'd be happy to help test the new instrumentations whenever you need help.

[david-luna]

There was a discussion in latest OTel JS SIG abut the location of this package (https://docs.google.com/document/d/1tCyoQK49WVcE-x8oryZOTTToFm7sIeUhxFPm9g-qL1k/edit#heading=h.ry29ajruzxyg)).

The conclusion was to move it to https://github.com/open-telemetry/opentelemetry-js-contrib
Link to the PR: open-telemetry/opentelemetry-js-contrib#1951