fix: delete sentry integration

[oliverb123]

We don't support this mode of using posthog error tracking, so this code is ~entirely unmaintained. I'm fairly sure if anyone /did/ try to use it, it'd send invalid data to posthog, which our pipeline would drop. Tearing it out as part of general SDK improvement work, first step in improving our django middleware/integration offering.

[greptile-apps]

PR Summary

Comprehensive removal of unmaintained Sentry integration from posthog-python SDK to prevent potential data quality issues and prepare for improved Django middleware.

• Removed entire sentry_django_example directory and posthog/sentry module, including all integration code and examples
• Cleaned up dependencies in pyproject.toml by removing 'sentry' optional dependency group and related packages
• Simplified exception_utils.py by removing Sentry-specific documentation while preserving core functionality
• Removed Django Sentry integration documentation from README.md to prevent users from implementing unsupported patterns

_{13 files reviewed, 1 comment
Edit PR Review Bot Settings | Greptile}

[daibhin]

I know this is technically a breaking change but seems like a pretty niche feature to necessitate a major upgrade for 🤔 Don't suppose there's anything we could bundle in as part of this change like we did for Node recently?

[oliverb123]

Version numbers are free, they let you make them as high as you want, even the major ones 😉.

More seriously, the next breaking change I want to make to this SDK is to make it optional to pass a distinct ID, and that's too large a change to bundle in here IMO. I'm not aware of anyone else working on anything breaking, and I think "biting the bullet" of major version bump for a relatively niche feature here wins us some credibility about future breaking changes.