Expand `record_lost_event` to Provide Envelope/Event Data and Integration Data

### Problem Statement

Hello!

Currently [record_lost_event](https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/transport.py#L132) is very limited and only provides `event_processor` as the reason to why an event was dropped. It is also missing data on what type of event depending (specifically on the dedup integration).

What is being dropped and why it is being dropped is important for the consumers of the API and can be used to track their own telemetry.

### Solution Brainstorm

Expose the event and what integration acted upon the event