feat(mysql2): support Connection.execute

[aptomaKetil]

Which problem is this PR solving?

The current instrumentation for mysql2 does not track queries made with Connection.execute, which is the helper method for preparing and executing a statement.

Short description of the changes

Since Connection.query and Connection.execute have the same signature and response formats (where it matters), all the existing wrapper code can simply be reused.

Tests for Connection.query and Pool.query have been mirrored for .execute.

Checklist

• Ran npm run test-all-versions for the edited package(s) on the latest commit if applicable.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aptomaKetil / name: Ketil Øvrebø (081058e)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aptomaKetil / name: Ketil Øvrebø (081058e)
• ✅ login: Rauno56 / name: Rauno Viskus (6520476)

[rauno56]

Looks good. Thanks, @aptomaKetil, and congrats for the first contribution!
I'll keep the PR open for a day or so more for others to see and react to it.

Please sign the CLA.

[codecov]

Codecov Report

Merging #1028 (32b4984) into main (0dc580d) will increase coverage by 0.11%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main    #1028      +/-   ##
==========================================
+ Coverage   95.91%   96.02%   +0.11%     
==========================================
  Files          13       16       +3     
  Lines         856     1006     +150     
  Branches      178      206      +28     
==========================================
+ Hits          821      966     +145     
- Misses         35       40       +5     

Impacted Files	Coverage Δ
...etry-instrumentation-mysql2/src/instrumentation.ts	94.36% <80.00%> (ø)
.../opentelemetry-instrumentation-mysql2/src/utils.ts	100.00% <0.00%> (ø)
...tapackages/auto-instrumentations-node/src/utils.ts	97.95% <0.00%> (ø)

[blumamir]

Edit: I see now that the options argument has the sql property on it so it should be compatible and it is covered in tests. LGTM, thanks for the contribution.

> Since Connection.query and Connection.execute have the same signature.

I am not sure that's right. execute accepts calls like this:

// execute(options, cb)

Where the sql value is set in options and not as first function parameter

[dyladan]

I thought in some versions of this query actually called execute which would result in double spans. Are you sure this is not the case?

[aptomaKetil]

I thought in some versions of this query actually called execute which would result in double spans. Are you sure this is not the case?

The tests for execute all have assertions on the number of spans produced by the instrumentation, so this is covered. I'm unaware of any previous discussion around this. I've taken a brief look at the mysql2 source and as far as I can tell, query and execute are on completely different code paths.

[rauno56]

Thanks, @aptomaKetil and congrats for your first contribution!