fix: ensure correct signal delivery on multi-client setups

[giortzisg]

Description

Previously logs and metrics were coupled with the sentry.client, this created these problems on multi client setups:

• when using WithCtx on multi client setups, if the passed context/hub was on a new client, the signal was captured on the old client (used on initialization)
• if bindClient was used on hub, the client which was set wasn't respected.
• the resolveScopeAndTrace was falling back to the CurrentHub. In multi client setups this means that the fallback hub would always be the one from the most recent client, since the Init method always binds the new client on the CurrentHub.

The PR solves all issues by coupling logs and metrics with the Hub and not the Client. This way we always can fall back to the Hub provided on logger/metric init, rather than a client which may have been mutated with bindClient or the CurrentHub which would return the most recent client.

Issues

Changelog Entry Instructions

To add a custom changelog entry, uncomment the section above. Supports:

• Single entry: just write text
• Multiple entries: use bullet points
• Nested bullets: indent 4+ spaces

For more details: custom changelog entries

Reminders

• Add GH Issue ID & Linear ID
• PR title should use conventional commit style (feat:, fix:, ref:, meta:)
• For external contributors: CONTRIBUTING.md, Sentry SDK development docs, Discord community

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

New Features ✨

• Log specific message for RequestEntityTooLarge by giortzisg in #1185

Bug Fixes 🐛

• Ensure correct signal delivery on multi-client setups by giortzisg in #1190

Internal Changes 🔧

• (deps) Bump getsentry/craft from 2.19.0 to 2.20.1 by dependabot in #1187
• Rename Telemetry Processor components by giortzisg in #1186

---

_{🤖 This preview updates automatically when you update the PR.}