Prevent mongodb instrumentation from applying to async/reactive clients

[jasonjkeller]

The mongodb-3.0, mongodb-3.1, and mongodb-3.7 instrumentation modules could incorrectly apply to the async/reactive mongo drivers which they are not intended to do. This can cause issues such as segment timeouts and incorrect metrics due to asynchronous behavior that the instrumentation isn't intended to handle.

This is a followup to #341

This change means that some customers will lose visibility into mongodb calls where the async/reactive mongo drivers were being erroneously instrumented.

It also resolves an issue where both the mongodb-3.1 and mongodb-3.7 could apply.

Issue #198 is intended to add instrumentation for the async/reactive mongo drivers.

---

Tested with an app that was using a few different versions of the reactive client:

• mongodb-driver-reactivestreams:1.12.0 with mongodb-driver-core:3.11.2
• mongodb-driver-reactivestreams:4.2.3 with mongodb-driver-core:4.2.3

As expected none of the mongodb instrumentation modules loaded:

Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-2.12/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-2.14/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-3.0/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-3.1/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-3.7/1

---

Tested with an app that was using the sync client:

• mongodb-driver-sync:4.1.1 with mongodb-driver-core:4.1.1

As expected, only the mongodb-3.7 instrumentation loaded:

Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-2.12/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-2.14/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-3.0/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-3.1/1

Supportability/WeaveInstrumentation/Loaded/com.newrelic.instrumentation.mongodb-3.7/1
Supportability/WeaveInstrumentation/WeaveClass/com.newrelic.instrumentation.mongodb-3.7/com/mongodb/MongoClientSettings$Builder
Supportability/WeaveInstrumentation/WeaveClass/com.newrelic.instrumentation.mongodb-3.7/com/mongodb/MongoClientSettings

Tested with an app that was using the sync client:

• mongodb-driver-sync:3.6.3 with mongodb-driver-core:3.6.3

As expected, only the mongodb-3.1 instrumentation loaded:

Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-2.12/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-2.14/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-3.0/1
Supportability/WeaveInstrumentation/Skipped/com.newrelic.instrumentation.mongodb-3.7/1

Supportability/WeaveInstrumentation/Loaded/com.newrelic.instrumentation.mongodb-3.1/1
Supportability/WeaveInstrumentation/WeaveClass/com.newrelic.instrumentation.mongodb-3.1/com/mongodb/MongoClientOptions
Supportability/WeaveInstrumentation/WeaveClass/com.newrelic.instrumentation.mongodb-3.1/com/mongodb/MongoClientOptions$Builder

---

AITs pass: https://javaagent-build.pdx.vm.datanerd.us/job/AIT_Configurable/127/

Instrumentation tests pass for all three modified instrumentation modules.

[tbradellis]

lgtm
AND...All checks have passed (so pretty). 👍 🎉