feat(shorebird_cli): add shorebird release get-apks command

[bryanoltman]

Description

Adds the shorebird release get-apks command, which enables the creation of either a universal APK or spilt APKs from an existing Shorebird release.

Fixes #2423

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore
• 🧪 Tests

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[felangel]

Sorry I didn't weigh in on this earlier but I feel like the simpler solution would've been to adjust shorebird preview to output the location of the artifact that's being run and then folks can do whatever they want with the artifact without us having to introduce a brand new command and lots of additional code that we need to maintain.

Update: opened a PR with my suggested solution at #2587

[eseidel]

This comes up often. I'm not particularly wedded to one solution or the other (approved Felix's just because it was earlier in my inbox and I approve things sent to me).

Downloading the AAB and running bundletool are two things which are hard to do. Unclear if they should be tied together, but users don't know how to do either without our assistance. The logging solution Felix posted maybe is enough? The intent for preview might be different from the intent from this command however. Both need to have keystores in order to build the apk from an aab, the "preview" one might be using a local signing keystore, where as some other command might be using some sort of release key-store. Although one could argue if you're doing release work, why isn't it just from the original shorebird release.

[felangel]

This comes up often. I'm not particularly wedded to one solution or the other (approved Felix's just because it was earlier in my inbox and I approve things sent to me).

Downloading the AAB and running bundletool are two things which are hard to do. Unclear if they should be tied together, but users don't know how to do either without our assistance. The logging solution Felix posted maybe is enough? The intent for preview might be different from the intent from this command however. Both need to have keystores in order to build the apk from an aab, the "preview" one might be using a local signing keystore, where as some other command might be using some sort of release key-store. Although one could argue if you're doing release work, why isn't it just from the original shorebird release.

Yeah I'm not strongly opposed to a new command was just mostly trying to offer a simpler alternative that I believe would address the customer ask 🤷

[felangel]

shorebird preview has almost identical logic so it would be nice to refactor to share more code rather than having this implementation live in two separate commands

[bryanoltman]

Happy to, although the code shared between here and preview is split across several different places to accommodate both iOS and Android, and has a preview-specific cache that I was a bit hesitant to interact with here.

[bryanoltman]

This specific bit of code has also diverged, as preview always generates a universal APK and this command offers a way to disable that, so I'm less certain how much can be shared