feat(android): can we bundle Chromium using a dynamic feature module to give us better support on downlevel versions?

[mcdurdin]

One blocker we have for moving forward with modern web technologies in Keyman Engine for Web is that we continue to support very old versions of Android, which may have outdated versions of Chrome (System Webview) installed. It is possible to bundle a custom version of Chromium into the app to mitigate this. However, this would mean the app grows significantly in size, so we wouldn't want to do this unless we could restrict this additional size burden to the older devices (yes, that may also be problematic?)

This would untie us from the requirement to work with very old versions of Chrome.

See:

• https://developer.android.com/guide/playcore/feature-delivery#dynamic_feature_modules
• https://engineering.fb.com/2022/09/30/android/launching-a-new-chromium-based-webview-for-android/

Alternative: we already check Chrome version on Android I believe; can we simply prompt user to update more aggressively?

[darcywong00]

Just jotting a note that even the Android 8.1 (API 27) has an out of date Chrome 61.0 so suggestions don't appear due to console error (minimum required 95.0)

[darcywong00]

Possibly depends on #5454 to publish in Android App Bundle instead of the current apk.