Atrium 1.0.2

Removes a Google-only blob from the APK, and does the groundwork for the F-Droid
listing. No functional changes.

If you are still on 1.0.0, read the 1.0.1
notes first. It
fixed a security issue and you should rotate your Sonarr and Radarr API keys.

What changed

The Android Gradle Plugin writes an encrypted list of an app's dependency tree
into the APK signing block, so that Google Play Console can read it. It was in
every Atrium APK, including the published 1.0.0 and 1.0.1:

0x7109871a  v2 signature
0x504b4453  dependency metadata   <- this
0x42726577  padding

Nothing ever transmitted it. It is passive, and only read if an APK is uploaded
to Play, which Atrium never is. So the no-telemetry promise was never affected.
But nothing here reads it back either, F-Droid will not publish an APK carrying
a blob it cannot inspect, and an encrypted Google artifact has no place in a
GPL app you are trusting with server credentials. It is now switched off, and
verified gone from all three ABIs.

Also fixes a bug in the repo's own build helper: it walked into the pub cache
and ran code generation inside downloaded dependencies whenever the cache lived
inside the checkout.

Which APK

Most phones want app-arm64-v8a-release.apk. Use armeabi-v7a for older
32-bit devices, and x86_64 only for emulators and Chromebooks. Android 7.0
(API 24) or newer.

Signed with the same key as 1.0.0 and 1.0.1 (CN=Atrium, O=Atrium), so this
installs as a normal update. apksigner verify --print-certs should report:

5ebad1ff2f9cdc63f28b364addf9e858330db26909d9eba8dfbccb998de37351

Free software under the GPL-3.0-or-later.