chore: remove unused InstrumentationConfig#path

[Flarna]

Which problem is this PR solving?

Short description of the changes

Removed the unused field InstrumentationConfig#path as it seems it's not used anywhere. The comment there is also outdated so can't tell if it was ever used.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

CI

Checklist:

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

[codecov]

Codecov Report

Merging #2944 (5aa6f8b) into main (ddb0775) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2944   +/-   ##
=======================================
  Coverage   92.97%   92.97%           
=======================================
  Files         185      185           
  Lines        6089     6089           
  Branches     1304     1304           
=======================================
  Hits         5661     5661           
  Misses        428      428           

[Flarna]

Actually I'm not sure if changes like this in experimental modules should be marked as breaking or housekeeping.

[blumamir]

Actually I'm not sure if changes like this in experimental modules should be marked as breaking or housekeeping.

I think it's ok to mark it as chore in this case

[legendecas]

There is an upgrade guideline https://github.com/open-telemetry/opentelemetry-js#upgrade-guidelines that describes the (possible) breaking changes with experimental versions. Maybe we can add an entry to it. Either way, this is lgtm.