The Release CI workflow is currently failing, likely due to the minimum required Android SDK Build-tools version for `macos-latest` GitHub-hosted runners being updated to 33.0.2, while the version used in https://github.com/kevin-david/zipalign-sign-android-release is 32.0.0.
Changes made in this PR include:
- Upgraded Java version from 17 to 21.
_(Updated to `noriban/sign-android-release` in both workflows, seems to be more updated recently)_
_(Enabled by default in `noriban/sign-android-release`)_
- Automatically determined and utilized the latest installed Build Tools version for APK signing.
- Utilized `${{steps.sign_app.outputs.signedReleaseFile}}` to point to the signed APK files.
- Utilized `${GITHUB_SHA::7}` to obtain the short Git version hash in Debug CI
- Removed the 'Git branch name' step in Debug CI (no longer used, I guess?!)
- Removed the 'Delete unsigned file' step (redundant in Release CI since we can directly upload `${{steps.sign_app.outputs.signedReleaseFile}}`).
- In Debug CI delete unsigned files right before renaming the signed ones.
- In Release CI switch to `softprops/action-gh-release` since `marvinpinto/action-automatic-releases` is no longer maintained.
