Research if armeabi-v7a APK is still needed

[latin-panda]

Describe the issue
Previously we used to generate 3 APK

After removing XWalk we now generate 2 APK for WebView:

If we try to publish these two in Play Store, then we get the following error:

The 100009900 corresponds to the armeabi-v7a one and 100009901 corresponds to arm64-v8a. The error goes away if we only publish cht-android-v1.0.0-unbranded-arm64-v8a-release.apk.

Research if we still need the armeabi-v7a architecture. If we don't need it anymore then remove this architecture so we only generate 1 APK.

We were ignoring WebView armeabi-v7a before, see how we weren't including this in the github release and how it was commented in fastlane

[jkuester]

Just adding some context from a recent Slack thread:

We should be able to attach multiple apks to a release as long as the apks have been built with different versionCode values. Doing that would be technically possible, but would require changes to our current CI processes. If we decide we need this support, we should also consider just packaging as an aab file since I think we could support multiple arch's from the same package that way... (Though we did back away from aabs in the past so there are probably extra challenges to deal with from that angle.)