WIP: chore: DEVPLAT-6523 bump deps to latest minor/patch within major

[AndrewHart102]

Ran go get -u ./... and go mod tidy to pull in available minor/patch updates across direct and indirect dependencies. Notable direct bumps: dd-trace-go v2.4.0 → v2.8.1, grpc v1.77.0 → v1.81.0, redis/go-redis/v9 v9.17.2 → v9.19.0, franz-go v1.20.5 → v1.21.1, aws-sdk-go-v2 service modules, mage v1.15.0 → v1.17.2, plus minor logrus/protobuf/mysql bumps.

getsentry/sentry-go is intentionally pinned at v0.40.0; v0.46.0 removed Event.Extra (used in pkg/tracking/sentry.go) and needs a separate migration to Event.Contexts.

Description

Testing considerations

Checklist

• Prefixed the PR title with the JIRA ticket code
• Performed simple, atomic commits with good commit messages
• Verified that the commit history is linear and commits are squashed as necessary
• Thoroughly tested the changes in development and/or staging
• Updated the README.md as necessary

Related links

• #XYZ
• JIRXXX
• Design Document
• Slack discussion

---

Note

Medium Risk
Upgrades a large set of runtime and instrumentation dependencies (Datadog tracing, AWS SDK, gRPC/protobuf, Redis, etc.), which can introduce behavioral changes at runtime. Also changes how Logrus fields are attached to Sentry events (Extra → Contexts), which may affect error observability payloads.

Overview
Updates go.mod/go.sum with broad minor/patch dependency bumps, including Datadog dd-trace-go, AWS SDK v2 modules, google.golang.org/grpc, protobuf, redis/go-redis, franz-go, mage, mysql, and many indirect libraries.

Migrates Sentry logging integration in pkg/tracking/sentry.go to accommodate newer sentry-go by moving Logrus entry data from Event.Extra into Event.Contexts under a logrus context.

^{Reviewed by Cursor Bugbot for commit 3d2b87c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3d2b87c. Configure here.}

[cursor]

sentry-go bumped despite being explicitly pinned at v0.40.0

High Severity

The PR description explicitly states getsentry/sentry-go is "intentionally pinned at v0.40.0" and that the migration from Event.Extra to Event.Contexts "needs a separate migration," yet the dependency was bumped to v0.46.2 and the code was changed inline. The migration from Extra to Contexts wrapping all logrus fields under a "logrus" context key is a behavioral change — data previously surfaced as flat "Additional Data" in Sentry now appears nested under a named context, which can break existing Sentry alerts, dashboards, and search queries that reference those fields.

Additional Locations (1)

• pkg/tracking/sentry.go#L61-L62

 

^{Reviewed by Cursor Bugbot for commit 3d2b87c. Configure here.}