feat(mongo): add SpanNameResolver for customizable span naming

[Azer0s]

This PR adds a SpanNameResolver function to the monitor options in order to customize the span name to the users needs. This is especially relevant when dealing with multiple database instances, having to prefix spans, or generally needing to customize the span name.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Azer0s / name: Ariel Simulevski (2080be1, 366e609, 3c19c17, 57d402e, 5be5fce, 6a37008, 6ba4aaf, 789bc91, 7a32b50, 807588d, 84369b9, 8c74f35, 920c343, ac9e992, b85b0fc, bcd70d5, c185814, f9f2c52)

[dmathieu]

This will need a changelog entry.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.6%. Comparing base (15b3445) to head (6ba4aaf).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #7986     +/-   ##
=======================================
+ Coverage   78.5%   78.6%   +0.1%     
=======================================
  Files        184     184             
  Lines      14673   14683     +10     
=======================================
+ Hits       11520   11543     +23     
+ Misses      2802    2789     -13     
  Partials     351     351             

Files with missing lines	Coverage Δ
...godb.org/mongo-driver/v2/mongo/otelmongo/config.go	100.0% <100.0%> (ø)
...ngodb.org/mongo-driver/v2/mongo/otelmongo/mongo.go	88.4% <100.0%> (-0.2%)	⬇️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Azer0s]

This will need a changelog entry.

I added one

[Azer0s]

@dmathieu could you please merge? :)

[dmathieu]

We require 2 approvals to merge.

[Azer0s]

Ping @prestonvasquez :)

[flc1125]

I cannot be certain, currently for reference only:

Why can't this part func(collection, command string) string be func(collection string, evt *event.CommandStartedEvent) string

cc @prestonvasquez

[Azer0s]

Another option would be to pass a formatter data struct like so:

type FormatterData struct {
    *event.CommandStartedEvent
    CollectionName string
}

But tbh I don't really see what added benefits that would bring, but I am also not opposed to implementing it ☺️

[dmathieu]

I don't know enough about mongo to say what we need.
But with HTTP instrumentations, we pass the *http.Request object, so folks can use anything within that struct to build the span name.

[Azer0s]

@dmathieu should I change the formatter function to accept an event alongside the collection name?

[Azer0s]

I still feel like a formatter data struct is more extendable

[dmathieu]

@prestonvasquez is currently on leave. I have emailed his coworkers. Let's wait a bit for their input.

[Azer0s]

@dmathieu Hi! Are there any updates on this?

[donkahlero]

I'd also would like to ask if there are any updates regarding this, as I am in need for this change, as well. Thx!