feat: log captured exceptions

[daibhin]

Adds a log_captured_exceptions config option so that all $exception events can also be logged

This is useful internally to capture exceptions if our own product is unavailable.

We have a version of this already in https://github.com/PostHog/posthog/blob/c2c65827b31b13c8e2e84d4ddc33df34b5924487/posthog/exceptions.py#L58-L66 but that only applies to DFR views.

By doing this at the SDK level we can log any exception that is being captured. One difference is that the logger in the SDK is not structured but I think that's ok

[greptile-apps]

PR Summary

This PR adds a new configuration option log_captured_exceptions to the PostHog Python SDK, allowing exceptions captured via capture_exception to be logged locally in addition to being sent to PostHog.

• Added log_captured_exceptions boolean parameter to Client class constructor with default value of False
• Implemented logging logic in capture_exception method to log exceptions with additional context when enabled
• Added **kwargs parameter to module-level capture_exception function to pass through additional context
• Added test case test_capture_exception_logs_when_enabled to verify logging behavior
• Updated version from 3.23.0 to 3.24.0 in version.py and documented the feature in CHANGELOG.md

_{5 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[daibhin]

Currently blocked by failing tests. Fix in #216