This spike is scoped to the following:

• Determine if the existing opentelemetry-instrumentation-pymongo package can be used as the underlying implementation for PyMongo's OpenTelemetry support in accordance with the spec.
• If opentelemetry-instrumentation-pymongo isn't suitable for implementing the spec, can we contribute to it upstream to make it suitable? Or are we better off creating our own internal solution?
• The spec details specific OpenTelemetry span attributes to be recorded for each driver operation. What does that recording look like over the lifecycle of a PyMongo operation?
• Can we use our existing debug logging code to guide our OpenTelemetry support?
• Does abstracting both debug logging and OpenTelemetry logging into a single, centralized design make sense? Both appear to gather similar information at similar points, reducing duplication would be ideal.