feat: new fastify instrumentation

[obecny]

Which problem is this PR solving?

• Fixes New Instrumentation - fastify #551

Short description of the changes

• new instrumentation for fastify

[codecov]

Codecov Report

Merging #611 (ff5924c) into main (25b93bb) will decrease coverage by 0.16%.
The diff coverage is 100.00%.

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

@@            Coverage Diff             @@
##             main     #611      +/-   ##
==========================================
- Coverage   96.86%   96.69%   -0.17%     
==========================================
  Files           9       16       +7     
  Lines         638     1029     +391     
  Branches      126      159      +33     
==========================================
+ Hits          618      995     +377     
- Misses         20       34      +14     

Impacted Files	Coverage Δ
...entelemetry-instrumentation-fastify/src/version.ts	100.00% <100.00%> (ø)
...strumentation-fastify/test/instrumentation.test.ts	96.88% <0.00%> (ø)
...try-instrumentation-fastify/src/instrumentation.ts	97.29% <0.00%> (ø)
...entelemetry-instrumentation-fastify/src/version.ts	100.00% <0.00%> (ø)
...opentelemetry-instrumentation-fastify/src/utils.ts	90.00% <0.00%> (ø)
...telemetry-instrumentation-fastify/src/constants.ts	100.00% <0.00%> (ø)
...nstrumentation-fastify/src/enums/AttributeNames.ts	100.00% <0.00%> (ø)

[naseemkullah]

cc @mcollina in case you'd like to take a look (your feedback for pino instrumentation was helpful!), file of most interest: plugins/node/opentelemetry-instrumentation-fastify/src/instrumentation.ts 🙏

[mcollina]

Feel free to ping me whenever you need for all instrumentations of Fastify.

[YanivD]

Just a small note -
Can you add @opentelemetry/instrumentation-fastify to Node Instrumentations list?
All merged packages are updated in #638

[carlosalberto]

Ping @mcollina ;)

[obecny]

@blumamir appreciate the detailed review, pls have a look I either fixed or commented. Just still not sure about the export problems you mentioned

[blumamir]

@blumamir appreciate the detailed review, pls have a look I either fixed or commented. Just still not sure about the export problems you mentioned

Thanks for addressing the review. Added comments and examples on the open issues.
I understand if some of these issues are things you choose to not fix in the scope of this PR. I can also offer my help (here or in slack) in discussing possible solutions to the above cases if you like.

[obecny]

@blumamir addressed the last things, the one you added and the fixes we discussed, please check how it looks now. Thx for all suggestions and samples

[blumamir]

As discussed with @obecny , we think this PR is ready to be merged as is, and later fixes and enhancements can be added later as follow-up PRs.
Since it's currently not in release-please config, it will not be published to npm, allowing me to add a few fixes before it goes public