[SR] Recursive unmasking

### Problem Statement

Currently, [unmasking a component](https://docs.sentry.io/platforms/react-native/session-replay/privacy/#general-masking-rules) affects only the component directly wrapped with ``. For some use cases where the actual text components are two or more levels down in a nested component tree, this can become cumbersome and may also require unwanted updates to component code (e.g. several levels into a Button component - user wants to unmask the button label).

### Solution Brainstorm

Provide an API to mark a component for unmasking recursively.

Note: There was a conscious decision not do to this initially, because it makes it easy to unmask more than intended. If this is implemented, it should be very clear to the user what happens, and very hard/impossible to do it unintentionally.

E.g. something like `` (default: false)

---

There is currently no priority for this item. If you are interested in this, please upvote the issue 👍

Beginne mit der Überprüfung der bestehenden Sentry.Unmask API und der verknüpften React Native-Masking-Regeln. Definiere ein explizites rekursives Opt-in und das Verhalten seiner Nachfahren; überprüfe anschließend, dass verschachtelter Text nur auf Anfrage entmaskiert wird und dass das gewöhnliche Entmaskieren unverändert bleibt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.