fix(instrumentation): use all provided filepatches

[Ugzuzg]

Which problem is this PR solving?

Fixes the issue when only the first InstrumentationNodeModuleFile for each path is applied.

Fixes #2355

Short description of the changes

Filter and apply all InstrumentationNodeModuleFiles instead of just finding the first.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

• Added a unit test with multiple InstrumentationNodeModuleFile targeting the same file

Checklist:

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

[codecov]

Codecov Report

Merging #2963 (87d0285) into main (cb642d7) will decrease coverage by 0.01%.
The diff coverage is 90.00%.

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

@@            Coverage Diff             @@
##             main    #2963      +/-   ##
==========================================
- Coverage   92.66%   92.65%   -0.02%     
==========================================
  Files         187      187              
  Lines        6174     6178       +4     
  Branches     1305     1304       -1     
==========================================
+ Hits         5721     5724       +3     
- Misses        453      454       +1     

Impacted Files	Coverage Δ
...strumentation/src/platform/node/instrumentation.ts	63.73% <90.00%> (+0.51%)	⬆️

[dyladan]

I reran the browser test and it still failed in the same way. weird because this doesn't touch any browser code.

[Ugzuzg]

A different test is failing each time:
https://github.com/open-telemetry/opentelemetry-js/runs/6411704988?check_suite_focus=true#step:8:2771
https://github.com/open-telemetry/opentelemetry-js/runs/6412047147?check_suite_focus=true#step:8:2699
https://github.com/open-telemetry/opentelemetry-js/runs/6411208084?check_suite_focus=true#step:8:2702

I've also tried running it locally multiple times, but sadly, all the tests pass. :(

[pichlermarc]

I reran the browser test and it still failed in the same way. weird because this doesn't touch any browser code.

@dyladan the failing tests here seem to be related to #2852. It's predominantly the tests for instrumentation-fetch. I've seen it across multiple PRs.

[Ugzuzg]

I think, I have a fix for these tests here: #2969