Group otel-related updates into single PRs.

[blkt]

Summary

This should make merging dependabot PRs about tracing easier to handle.

Change Type

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[eleftherias]

Should we also group them with the otel upgrades? I see the splunk package we use are splunk-otel-go

[coveralls]

coverage: 53.146% (+0.004%) from 53.142%
when pulling f8f6f52 on chore/dependabot-group-splunk-otel-go
into 967f7d1 on main.

[blkt]

They were released some days apart from one another, I guess the impact would be that we would delay upgrading otel-only dependencies in that case. I'm ok if we want to merge them together.

This PR is mainly to avoid having two PRs as we do in this very moment

• one upgrading only github.com/signalfx/splunk-otel-go/instrumentation/database/sql/splunksql
• the other upgrading both that and github.com/signalfx/splunk-otel-go/instrumentation/github.com/lib/pq/splunkpq

[blkt]

@eleftherias I couldn't root-cause the panics we had when both libraries were updated, but I integrated your suggestion.