Lack of instrumentation and accurate test for mysql poolCluster

[mrickard]

Description

A customer observed a loss of telemetry for mysql poolCluster. This gap in telemetry was missed in version tests for mysql pooling: these tests used createConnection (invoked in a setup script). Removing this showed that the agent was not creating segments for poolCluster queries.

Expected Behavior

versioned/mysql/basic-pool.tap.js test should pass when using a poolCluster connection, and not rely on instrumentation via createConnection

Steps to Reproduce

See @bizob2828 's changes in https://github.com/newrelic/node-newrelic/tree/mysql-fix

Running versioned tests in that branch will fail subtests in the poolCluster query test. For example, while transactions exist, no segment has been created.

Additional context

See https://issues.newrelic.com/browse/NR-116646

[workato-integration]

https://issues.newrelic.com/browse/NEWRELIC-8727

[workato-integration]

Jira CommentId: 204178
Commented by mrickard:

PR: #1647

Thanks to [~revans] for fixing this!