feat: adding instrumentation support for mongo-driver/v2

[AlaricWhitney]

Adding the mongo-driver/v2 instrumentation.

This is a copy/paste of the v1 instrumentation, and was modified to adhere to the mongo-driver/v2 requirements.

Notable differences:

• mtest was removed in v2. Replaced with drivertest in the unit testing.

This addresses PR #6419

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: AlaricWhitney / name: Alaric Whitney (0403896, d38d115, bd3c9c5, f6ec856, c40e17c, afa32f5, 9cf350b, a0f083b, 37c8729, 6d22da1, c0d2e16, b3cbb84, 95dcf65, 80b0e88, 9590887, 24b5f1e, f2cd406, 3cabc4a, f83a9ab, 407eea4, 6ab56e1, 7675b51, e97fcde, dd6d736, 8e90ad0, 4e44c3e, 71da688, 7b9fc3e, d9dbc54, ee21b89, 199af6e, 7c76a06)

[codecov]

Codecov Report

Attention: Patch coverage is 88.98305% with 13 lines in your changes missing coverage. Please review.

Project coverage is 75.8%. Comparing base (5b41ad8) to head (d9dbc54).

Files with missing lines	Patch %	Lines
...ngodb.org/mongo-driver/v2/mongo/otelmongo/mongo.go	85.7%	9 Missing and 4 partials ⚠️

Additional details and impacted files

@@          Coverage Diff           @@
##            main   #6539    +/-   ##
======================================
  Coverage   75.7%   75.8%            
======================================
  Files        207     210     +3     
  Lines      19403   19521   +118     
======================================
+ Hits       14695   14800   +105     
- Misses      4273    4282     +9     
- Partials     435     439     +4     

Files with missing lines	Coverage Δ
...godb.org/mongo-driver/v2/mongo/otelmongo/config.go	100.0% <100.0%> (ø)
...odb.org/mongo-driver/v2/mongo/otelmongo/version.go	100.0% <100.0%> (ø)
...ngodb.org/mongo-driver/v2/mongo/otelmongo/mongo.go	85.7% <85.7%> (ø)

🚀 New features to boost your workflow:

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

[dmathieu]

cc @prestonvasquez for review?

[prestonvasquez]

@AlaricWhitney Thank you for putting this together. I wanted to let you know that I'll be reviewing this in stages, as my schedule allows.

[jakenmbe]

can this pr merge? I need use it in my project

[dmathieu]

Not until all review comments have been closed an it has been approved.

[AlaricWhitney]

Could you add this new package to the CODEOWNERS file too?

This looks good. I don't have the required mongo knowledge to assert proper behavior though, so I'll let @prestonvasquez weigh on that.

@dmathieu Is there anyone particular I should add as the codeowner of this? I'm not 100% sure what the appropriate process is.

[AlaricWhitney]

@dmathieu @prestonvasquez This should be ready for review again.

For the CODEOWNERS I have added the entry but left the assignments as blank for now, pending your feedback on how you want to proceed with that.

[dmathieu]

Is there anyone particular I should add as the codeowner of this?

Keep it blank for now. Though we should probably add @prestonvasquez, if he's ok with it.

[prestonvasquez]

Is there anyone particular I should add as the codeowner of this?

Keep it blank for now. Though we should probably add @prestonvasquez, if he's ok with it.

@dmathieu @AlaricWhitney SGTM, thanks!

[dmathieu]

cc @MrAlias

This kinds of goes in the same way as this comment: #6961 (comment)

We should therefore adopt the same behavior. So let's keep commit hashes rather than releases for now (you just need to remove the entries in versions.yaml).

[AlaricWhitney]

Sounds good. I'll remove the entries from versions.yaml. I'm unsure what needs to be done about the commit hashes, as I don't see any action taken yet with the referenced PR.

[dmathieu]

You should still add it to excluded modules in versions.yaml, so it doesn't get released. But it gets dependency upgrades on a new release.

[AlaricWhitney]

got it. I added it to the excluded modules.