fix(instrumentation-mysql2): instrument connection on 3.11.5

[pichlermarc]

Description:

[email protected] did include a refactoring that moved some of the functionality we instrument to a base class. This PR adapts to instrumenting the base class instead if one exists and the name of the base is known to us.

Fixes #2572

[codecov]

Codecov Report

Attention: Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.75%. Comparing base (8bfa21f) to head (705a6a4).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
.../opentelemetry-instrumentation-mysql2/src/utils.ts	87.50%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2579      +/-   ##
==========================================
- Coverage   90.75%   90.75%   -0.01%     
==========================================
  Files         169      169              
  Lines        8018     8026       +8     
  Branches     1632     1635       +3     
==========================================
+ Hits         7277     7284       +7     
- Misses        741      742       +1     

Files with missing lines	Coverage Δ
...etry-instrumentation-mysql2/src/instrumentation.ts	94.66% <100.00%> (ø)
.../opentelemetry-instrumentation-mysql2/src/utils.ts	93.18% <87.50%> (-1.27%)	⬇️

[david-luna]

This reminds me of #2522
What would you think about checking the presence of the functions in the base class' prototype?

[pichlermarc]

good idea, let's try that, one sec.

[pichlermarc]

@david-luna doing that now (see latest commits)