feat: add initial DataCollection struct

[giortzisg]

Description

This adds the initial datastructures and logic for implementing the https://develop.sentry.dev/sdk/foundations/client/data-collection/#overview spec.

#skip-changelog

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

🟡 Minor (new features)

📋 Changelog Preview

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

---

This PR will not appear in the changelog.

---

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

[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 eb379b3. Configure here.}

[cursor]

Integrations ignore resolved DataCollection

Medium Severity

NewClient resolves and stores DataCollection, but leaves SendDefaultPII unchanged and existing instrumentation (for example SQL db.user) still gates on Options().SendDefaultPII. With an explicit DataCollection pointer—including an empty struct whose resolved UserInfo defaults to true—GetDataCollection can disagree with what integrations actually collect, contrary to the option comment that SendDefaultPII is ignored when DataCollection is set.

 

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