Upgrade semconv to 1.32.0 for otelmongo

[MrAlias]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.4%. Comparing base (15cb04e) to head (9d9177b).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #7393   +/-   ##
=====================================
  Coverage   82.4%   82.4%           
=====================================
  Files        205     205           
  Lines      18084   18084           
=====================================
  Hits       14906   14906           
  Misses      2741    2741           
  Partials     437     437           

Files with missing lines	Coverage Δ
.../mongo/otelmongo/internal/semconv/event_monitor.go	100.0% <100.0%> (ø)
...ngodb.org/mongo-driver/v2/mongo/otelmongo/mongo.go	88.5% <ø> (ø)

🚀 New features to boost your workflow:

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

[prestonvasquez]

@MrAlias The doc.go file should be updated to reflect this update:

// The "OTEL_SEMCONV_STABILITY_OPT_IN" environment variable can be used to opt
// into the latest semantic version:
//   - "database": emit latest semantic conventions
//   - "": emit v1.21.0 (default) semantic conventions
//   - "database/dup": emit v1.21.0 (default) and latest
//
// By default, otelmongo only emits v1.21.0.

It might also be helpful to list what the latest semantic version is.

[MrAlias]

Keeping the term "latest" prevents constant manual intervention and the inevitability of becoming out of sync. I prefer to keep the terms as they are.

Users with the desire for details on what version of semantic convention they are emitting can look at the produced telemetry scheme URL or the code they are reading this from .

[prestonvasquez]

Keeping the term "latest" prevents constant manual intervention and the inevitability of becoming out of sync. I prefer to keep the terms as they are.

Users with the desire for details on what version of semantic convention they are emitting can look at the produced telemetry scheme URL or the code they are reading this from .

@MrAlias I specifically added the word "latest" so you could just drop the update in. The current doc.go files specifies 1.26.0.

[MrAlias]

Keeping the term "latest" prevents constant manual intervention and the inevitability of becoming out of sync. I prefer to keep the terms as they are.
Users with the desire for details on what version of semantic convention they are emitting can look at the produced telemetry scheme URL or the code they are reading this from .

@MrAlias I specifically added the word "latest" so you could just drop the update in. The current doc.go files specifies 1.26.0.

Ah, gotcha. I misunderstood. Sounds like we are in favor of the same result.