Add before-capture-callback and debouncing for screenshots/view hierarchy

[markushi]

Right now there's little control over when screenshots or view hierarchies are captured. This can have a negative impact on the app performance itself (capturing many screenshots, contribution to quota) as well as the usability of the feature itself (no control when a screenshot should be taken or not).

Internal decision doc

Solution

• Add debouncing mechanism
• Introduce a BeforeCaptureCallback

Related Android PR: getsentry/sentry-java#2773

Tasks

Beta Give feedback

1. Add debouncing mechanism and before-capture callbacks for screenshots/vh sentry-java#2773
   +0
2. Add BeforeCaptureCallback - Screenshot sentry-cocoa#3137
   Platform: Cocoa Type: Feature Request +2
   
3. Add before-capture-callback and debouncing for screenshots/view hierarchy sentry-dart#1540
   Platform: Dart +1
   
4. Add before-capture-callback and debouncing for screenshots/view hierarchy sentry-react-native#3189
   Platform: React-Native +1
5. Unity

[stefanosiano]

Just a small explanation on what was done in Android.
We now have options.setBeforeScreenshotCaptureCallback and options.setBeforeViewHierarchyCaptureCallback
These callbacks have these parameters: event, hint and debounce (a flag which says the screenshot/vh should be debounced and ignored)
The callback can overwrite the debounce mechanism, forcing the screenshot/vh to be taken, or make it completely skipped.
here is the code for screenshots and view hierarchy