Get rid of pymongo command in pymongo instrumentation span name

[amitsetty]

As others have pointed out
open-telemetry/opentelemetry-java-instrumentation#341
by including the query within the span name we lead to very high cardinality which is too high to be useful and this can also lead to privacy concerns

This pull requests follows the logic found in the java and golang mongo instrumentations and does not include the entire command but the database name and command name within the span name

https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/mongo/mongo-3.1/library/src/main/java/io/opentelemetry/instrumentation/mongo/v3_1

https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/instrumentation/go.mongodb.org/mongo-driver/mongo/otelmongo/mongo.go

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• test_pymongo.py

Does This PR Require a Core Repo Change?

• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: amitsetty (620e8b5, ef3bb11, 081a1fd, 4a7b165)

[srikanthccv]

While at it could you please check what's the semconv recommendation for this? Also please add some tests.

[amitsetty]

Hey I checked the semconv recommendation and it seems like this is more in line with [https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/database.md](the conventions)

While being in line with all stated conventions there is an example within the conventions which shows instrumentation for a Mongo database. There is a small diff here where the example instrumentation contains a collection name - however the [https://api.mongodb.com/python/3.1/api/pymongo/monitoring.html](the pymongo library monitoring tool) does not return the collection name

More work could be done here in the future to try to add the collection name. In the meantime it is imperative that the instrumentation is in line with the overall database specification as having a very high cardinality leads the instrumentation to become a lot less useful

[amitsetty]

Hey would love if someone could review this