CI: suffix branch APKs with -phone and -wear_os for clarity

Without a target suffix, the phone APK on a wear branch reads as "the
main APK" and a tester might miss that the watch needs its own install.
Renaming both halves makes which-goes-where unambiguous in the rolling
pre-release asset list.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: eried

.github/workflows/branch-apk.yml

@@ -64,8 +64,8 @@ jobs:
           BRANCH="${GITHUB_REF##*/}"
           SHORT_SHA="$(git rev-parse --short HEAD)"
           TAG="branch-${BRANCH}"
-          APK_NAME="EUC-Planet-${BRANCH}-${SHORT_SHA}.apk"
-          WEAR_APK_NAME="EUC-Planet-${BRANCH}-${SHORT_SHA}-wear.apk"
+          APK_NAME="EUC-Planet-${BRANCH}-${SHORT_SHA}-phone.apk"
+          WEAR_APK_NAME="EUC-Planet-${BRANCH}-${SHORT_SHA}-wear_os.apk"
 
           # Pull the per-branch description if BRANCH.md exists, otherwise
           # fall back to a generic notice. This becomes the release body header.