bug(android): TransactionTooLargeExceptions occur

Sentry Issue: [KEYMAN-ANDROID-6XP](https://keyman.sentry.io/issues/6573929562/?referrer=github_integration)

```
RuntimeException: android.os.TransactionTooLargeException: data parcel size 1690520 bytes
Bundle stats:
android:viewHierarchyState [size=1688540]
android:views [size=1688432]
0x7f08012d [size=1687592]
androidx.lifecycle.BundlableSavedStateRegistry.key [size=1064]
PersistableBundle stats:
[null]
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:675)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1002)
...
(4 additional frame(s) were not displayed)

TransactionTooLargeException: data parcel size 1690520 bytes
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:675)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1002)
...
(8 additional frame(s) were not displayed)
```

Useful reference: https://yellowgnu.com/fix-transactiontoolargeexception-in-android-causes-examples-and-best-practices/

I've yet to investigate more deeply which of the potential causes may be at play here... and I wouldn't be terribly surprised if this interacts with the WebView.

Start with the linked Sentry issue and reproduce the Android TransactionTooLargeException, using the reported Bundle statistics to investigate saved view-hierarchy state. Check whether the WebView is involved and identify the affected screen or lifecycle path; done means the exception no longer occurs under the reproducing conditions.

Written by the indexing model from the issue text.