Update microG fix

Description

Related issues

• e/backlog#2184 (closed)
• e/backlog#2186 (closed)
• e/backlog#2246 (closed)
• e/backlog#2244 (closed)
• e/backlog#2245 (closed)
• e/backlog#2181 (closed)
• e/backlog#1975 (closed)
• https://gitlab.e.foundation/e/backlog/-/issues/2171

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Related MRs

How has this been tested?

Test is a little bit complicated as we have to use /e/ 0.13 to be able to manage between microG v2.14 and v2.17. Below how I proceed:

1. I install a v0.13 build on my device
2. From Apps, I install microG EN
   • Now Apps is in mode "update" for microG
   • but microG EN is in v2.17, so we can't test update.
3. I uninstall microG update from Settings > Apps
4. I manually install microG EN v2.14 signed with test keys microg-v2.14.apk
5. To be able to test updates from other app, I install SNCF_v10.75.1_apkpure.com.apk
6. Now I'm able to test... but not directly. v0.13 doesn't contain UI revamping stuff, so we can't use the APK from this branch. I use APK from the branch test-microg-fixes where I cherry-picked all commits from this branch. I sign the APK with platform test keys (here)

Author @rhunault

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules