initial fastlane structures from IzzyOnDroid

[IzzySoft]

this PR provides you with a "fastlane starter package". Some notes to sum them up in a place easy to find for you:

• the IzzyOnDroid Fastlane Documentation can guide you with maintaining the structures here
• take special care for limits, e.g. per-release changelogs can have max 500 chars, full_description.txt max 4,000 chars, graphics must have specific aspect ratios etc.
• you can have "bigger graphics" here; the IoD updater takes care to resize/optimize them as needed
• for the full_description.txt here I've used HTML compressed into a single line, to prevent the fdroid software converting each line break to a <br>. The tags used for this are supported by F-Droid.org as well, and to my knowledge even by PlayStore.
• whenever you add a new "type" of metadata that has not been there before (e.g. the first changelog, a featureGraphic if it wasn't yet present), please let us know so we can check and enable it.
• Details on all this in the linked documentation.
• Once merged, your changes will be synced whenever a new release is pulled in here – to make sure it stays up-to-date with the app itself.
• Should you have questions, be welcome to ask 😉

And now: Enjoy!

[IzzySoft]

A few notes for background: BruceApp was just added to the IzzyOnDroid repo, and will show up at https://apt.izzysoft.de/packages/bruce.app in about an hour. Be welcome to pick a badge and link there e.g. from your Readme! And as the app was also confirmed as Reproducible Build (see e.g. Reproducible Builds, special client support and more at IzzyOnDroid for details), there's also a shield becoming available in a few hours, which will show the latest known RB status:

[<img src="https://shields.rbtlog.dev/simple/bruce.app" alt="RB shield">](https://shields.rbtlog.dev/bruce.app)

The only thing our scanners complained about was:

SigningBlock blobs:
-------------------
0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE)

which can easily be avoided by adding a few lines to your build.gradle:

android {
    dependenciesInfo {
        // Disables dependency metadata when building APKs (for IzzyOnDroid/F-Droid)
        includeInApk = false
        // Disables dependency metadata when building Android App Bundles (for Google Play)
        includeInBundle = false
    }
}

For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. More details can be found e.g. here: Ramping up security: additional APK checks are in place with the IzzyOnDroid repo.

One last word concerns versioning. Your release tag says v0.3 – while the app itself identifies as

package: name='bruce.app' versionCode='1' versionName='1.0'

Can you please bring that in sync with future releases? The place to do so would be here. Please make sure to always increase versionCode with each release, and have versionName match the tag name (so currently, it should have been 0.3 instead of 1.0 – but please do not touch the existing release anymore to correct that, as that has already been distributed; just keep it in mind for future releases 😉)

Sneak preview from our staging area:

The green shield you see in the screenshots signals that release was confirmed as Reproducible Build.