Bring back lastEventId API

[Lms24]

Problem Statement

The king is dead, long live the king...

We removed lastEventId in #10585 due to several shortcomings of this API:

• It would return potentially unexpected event ids, for example when multiple errors were caught in sequence
• The last eventId was updated directly in captureEvent, before processing and sending the event. Meaning, if users or our event processors dropped the event, lastEventId would return an id of an event that wasn't ever sent from the SDK.
• Depending on how Hub was used, it could potentially bleed through requests/"leak" an event id of another request if there was no proper request isolation set up.

Solution Brainstorm

In an effort to minimize friction we should bring back this API:

• Store it on the isolation scope (--> ideally avoids cross-request bleeds on server; doesn't matter for browser)
• Update the last event id on the isolation scope directly before sending the event (i.e. when chances are low that the event is still dropped on the client side)
• Unchanged to previous implementation: only update the id with error events
• Add a big warning that this API returns potentially nonsense

Tasks

Beta Give feedback

1. feat(scope): Bring back lastEventId on isolation scope (#11951) #12022
   +0
2. ref(feedback): Make eventId optional and use lastEventId in report dialog #12029
   +0
3. ref(api): Remove lastEventId deprecation warnings (#11951) #12042
   +0
4. Update migration docs
5. ref(javascript): Revert lastEventId removal (v8) and deprecation (v7) in migration docs sentry-docs#10127
   +0
   

[Lms24]

Also ref: getsentry/sentry-python#3057 (comment)

[Lms24]

Python PR using isolationScope: getsentry/sentry-python#3064