Android 15 feature that uses a heuristic that detects passwords and logins plus content that explicitly calls setContentSensitivity.

This bug tracks the evaluation of if this feature works in android apps that have flutter views (add to app) and flutter apps that use android views (platform views). This includes a simple method channel implementation. See the issues below for tracking of further improvements.

Required for feature shipping

1. Land method channel implementation of content sensitivity.

Next steps

3. Use the feature in relevant Flutter widgets (sensitive TextFields, for instance) to exemplify usage of the feature and push adoption: [Android] Add SensitiveContent widget to Flutter widgets that have potential security vulnerabilities during screen share #167302

Stretch goals

3. Ensure every FlutterView has a unique ID for the native SensitiveContentPlugin to identify them by: [Android] Make FlutterView IDs instance variables instead of a static one #162685
4. Make the SensitiveContent widget sensitive to the visibility of child widgets: [Android] Un-mark sensitive content when it is not visible on screen #160051
5. Investigate and convert this PR to use JNIgen: [Android] Modify sensitive content support implementation to use JNIgen #160050
6. Implement autoSensitivity mode: [Android] Investigate implementing autoSensitive sensitive content mode #160879
7. Investigate backwards compatibility for APIs < 35: [Android] Consider implementing backwards compatibility for sensitive content protection #159208