fix(instrumentation): use caret range on import-in-the-middle

[pichlermarc]

Which problem is this PR solving?

import-in-the-middle is having a lot of changes right now to keep up with changes in Node.js. This PR unpins import-in-the-middle to ensure our users can also keep up without requiring a new @opentelemetry/instrumentation release each time.

This PR is intended as more of a discussion-starter. There are a few pros and cons to both sides (keeping it pinned vs. unpinning it)

Type of change

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

[codecov]

Codecov Report

Merging #4380 (3857159) into main (a512494) will increase coverage by 0.02%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4380      +/-   ##
==========================================
+ Coverage   92.21%   92.24%   +0.02%     
==========================================
  Files         333      333              
  Lines        9459     9459              
  Branches     2009     2009              
==========================================
+ Hits         8723     8725       +2     
+ Misses        736      734       -2     

see 2 files with indirect coverage changes

[legendecas]

I didn't find a clue why this was pinned. AFAICT, external dependencies are generally not pinned. Maybe @JamieDanielson can chime in?

[trentm]

I am okay with unpinning it. IOW, basically I trust the IITM authors to follow semver.

[dyladan]

I am also ok unpinning

[pichlermarc]

Alright, seems like no objections to unpinning - let's do that then. 🙂
I'm also going to cut a release as we need IITM 1.7.2 or later for the tests in contrib to pass.

[JamieDanielson]

I didn't find a clue why this was pinned. AFAICT, external dependencies are generally not pinned. Maybe @JamieDanielson can chime in?

FWIW I don't fully remember either, but I suspect it was probably intentional at the time because the initial instrumentation change was experimental and potentially delicate, so we were concerned about unexpected behavior if the exact version and behavior changed. At this point though it makes sense to follow our general guidelines, glad to see this got updated 👍