feat(oracledb): Add support for Oracle DB instrumentation

[sudarshan12s]

Add Oracledb instrumentation

Which problem is this PR solving?

Adding instrumentation support for node-oracledb applications connecting to Oracle database.

Short description of the changes

From node-oracledb version 6.7 onwards, oracledb module exports a class,
TraceHandlerBase which simulates interface kind of functionality with abstract methods to be overwritten by the derived class.

The current OT module derives this class TraceHandlerBase and implements abstract methods; It uses setTraceInstance method of oracledb module to register this new derived class OracleTelemetryTraceHandler
These methods are invoked by oracledb module providing the traceContext which is used to dump the data in to the span after converting to standard span attributes.

Following are the abstract methods implemented:

• onEnterFn -> It gets invoked by oracledb module when application invokes getConnection to create a connection to
  database or execute method to run a sql. It is invoked before invoking the public API calls made by application.
• onExitFn -> It gets invoked after the public API call is completed with success/failure.
• onBeginRoundTrip -> It gets invoked before round trip to database which was triggered as part of public API.
• onEndRoundTrip -> It gets invoked after round trip to database completes which was triggered as part of public API..

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: sudarshan12s / name: Sudarshan Soma (3cf1bd2, 77a08a7, 2b310c5, ae1b7ac, 6219bc4, b3bc7eb, 440db83, f670ac0, f8ff501, 7cccc2e, 7f00bf6, 382680c, 4c36312, 3774f0d, 01b2f84, c8e0be6, 30a2367, 474b6e3, 91d65e4, 6faff54, 34afcad, d25ee8e, 13e79db, a06b40f, 5c98035, 759ae13, bf73ff5, f41f62c, 604f833, e19e1ea, e076936, a0367cc, 34cd418, 90db232, 07c76fd, 0290b81, 92c1c80, 34ef02d, 365d523, c7fcb17, fa0463b, 3ae4d72, 2296e18, 5defed8, e1698e1, 5faff20, 5c4f37f, f98c7a4, 7e26da9, badc18a, 988eab2, d155fb8, 91136ce, 8ceff01, 5117f31, 3c600fe, 0e25652, 0704e73, 4a154e5, c299caa, c3a8da9, 93d21e1, f4b43e9, cbe5bd1, 12f6b2b, be90e6b, 23d2923, 8ce3e88, f018f0f, 1295e53, 966e487, 76b3f21, 9a0f07a)

[maryliag]

Thank you for addressing all comments. It's almost there :)
I added a few more comments, all easy to fix!

[maryliag]

I'm still seeing a lot of SEMATTRS_ here

[maryliag]

Great work on this!

[sharadraju]

Thanks @maryliag and @blumamir for your review and thanks @marcalff for the sponsor support!
@sudarshan12s Nice work!

[sudarshan12s]

Great work on this!

Thank you so much...

[sudarshan12s]

It looks like the failed test may be flaky (intermittently asserting different connection counts). Would it be possible to either ignore this failure for this PR, or re-run the CI?

MongoDBInstrumentation-Metrics
       Should add connection usage metrics:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

2 !== 1

      + expected - actual

      -2
      +1
      
      at Context.<anonymous> (test/mongodb-v4-v5-v6.metrics.test.ts:127:12)

Thanks for your time!

[sudarshan12s]

It looks like the failed test may be flaky (intermittently asserting different connection counts). Would it be possible to either ignore this failure for this PR, or re-run the CI?

MongoDBInstrumentation-Metrics
       Should add connection usage metrics:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

2 !== 1

      + expected - actual

      -2
      +1
      
      at Context.<anonymous> (test/mongodb-v4-v5-v6.metrics.test.ts:127:12)

Thanks for your time!

@onurtemizkan, I believe this is a flaky error and can be safely ignored.

[sharadraju]

Thanks @blumamir for merging this PR.