feat(android): Add screenshot strategy to session replay docs (#15270)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
- Add a new option `screenshotStrategy` which has been introduced in
this [PR](getsentry/sentry-java#4777) and allows
customers to specify a more reliable masking strategy.

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [x] Other deadline: Ideally next week
- [ ] None: Not urgent, can wait up to 1 week+

Author: romtsn

docs/platforms/android/session-replay/index.mdx

@@ -57,12 +57,22 @@ SentryAndroid.init(context) { options ->
 
   options.sessionReplay.onErrorSampleRate = 1.0
   options.sessionReplay.sessionSampleRate = 0.1
+  
+  // if your application has strict PII requirements we recommend using the Canvas screenshot strategy
+  // Note: this strategy is experimental and does **not** support any masking options, it always masks text and images
+  // Available in the Android SDK version 8.24.0 or above
+  // options.sessionReplay.screenshotStrategy = ScreenshotStrategyType.CANVAS
 }
 ```
 
 ```XML {filename:AndroidManifest.xml}
 <meta-data android:name="io.sentry.session-replay.on-error-sample-rate" android:value="1.0" />
 <meta-data android:name="io.sentry.session-replay.session-sample-rate" android:value="0.1" />
+
+<!-- if your application has strict PII requirements we recommend using the Canvas screenshot strategy -->
+<!-- Note: this strategy is experimental and does **not** support any masking options, it always masks text and images -->
+<!-- Available in the Android SDK version 8.24.0 or above -->
+<!-- <meta-data android:name="io.sentry.session-replay.screenshot-strategy" android:value="canvas" /> -->
 ```
 
 ## Verify
@@ -117,6 +127,32 @@ options.sessionReplay.maskAllImages = false
 <meta-data android:name="io.sentry.session-replay.mask-all-images" android:value="false" />
 ```
 
+### Screenshot Strategy
+
+The SDK offers two strategies for recording replays: `PixelCopy` and `Canvas`.
+
+`PixelCopy` uses Android's [PixelCopy](https://developer.android.com/reference/android/view/PixelCopy) API to capture screenshots of the current screen and takes a snapshot of the view hierarchy within the same frame. The view hierarchy is then used to find the position of controls such as text boxes, images, labels, and buttons and mask them with a block that's drawn over these controls. This strategy has slightly lower performance overhead but may result in masking misalignments due to the asynchronous nature of the PixelCopy API. We recommend using this strategy for apps that do not have strict PII requirements or do not require masking functionality.
+
+`Canvas` uses Android's custom [Canvas](https://developer.android.com/reference/android/graphics/Canvas) API to redraw the screen contents onto a bitmap, masking all `drawText` and `drawBitmap` operations in the process to produce a masked screenshot. This strategy has a slightly higher performance overhead but provides more reliable masking. We recommend using this strategy for apps with strict PII requirements.
+
+<Alert level="warning">
+
+The `Canvas` screenshot strategy is currently experimental and does **not** support any masking options. When the screenshot strategy is set to `Canvas`, it will **always** mask all texts, input fields and images, disregarding any masking options set. If you need more flexibility with masking, switch back to `PixelCopy`.
+
+</Alert>
+
+You can change the strategy as follows:
+
+```kotlin
+import io.sentry.ScreenshotStrategyType
+
+options.sessionReplay.screenshotStrategy = ScreenshotStrategyType.CANVAS // or ScreenshotStrategyType.PIXEL_COPY (default)
+```
+
+```XML {filename:AndroidManifest.xml}
+<meta-data android:name="io.sentry.session-replay.screenshot-strategy" android:value="canvas|pixelCopy" />
+```
+
 ## Error Linking
 
 Errors that happen while a replay is running will be linked to the replay, making it possible to jump between related issues and replays. However, it's **possible** that in some cases the error count reported on the **Replays Details** page won't match the actual errors that have been captured. That's because errors can be lost, and while this is uncommon, there are a few reasons why it could happen:

docs/platforms/android/session-replay/privacy/index.mdx

@@ -7,6 +7,12 @@ description: "Learn how to mask parts of your app's data in Session Replay."
 
 <Alert level="warning">
 
+The masking options below only apply when using the default `PixelCopy` strategy. If you set the strategy to [Canvas](/platforms/android/session-replay/#screenshot-strategy), those options will be ignored and all sensitive content (texts, inputs, images) will be **always** masked.
+
+</Alert>
+
+<Alert level="warning">
+
 Before enabling Session Replay in production, verify your masking configuration to ensure no sensitive data is captured. Our default settings aggressively mask potentially sensitive data, but if you modify these settings or update UI frameworks or system SDKs, you must thoroughly test your application. If you find any masking issues or sensitive data that should be masked but isn't, please [create a GitHub issue](https://github.com/getsentry/sentry-java/issues/new/choose) and avoid deploying to production with Session Replay enabled until the issue is resolved.
 
 </Alert>