Add PSDK Android compilation

[AerunDev]

As a game designer
I want to generate a playable Android build of my game directly from Pokémon Studio
So that I can distribute it on Android devices without relying on manual external packaging steps

Context

Currently, Pokémon Studio allows users to generate a playable version of a project only for the platform matching their local environment (Windows, Linux, etc.). This limits distribution, especially for Android, which is an important target platform for mobile players.

A first Android export flow already exists on the PSDK side through export_android.rb. This script packages the game into an Android APK based on a base PSDK APK template. More specifically, it:

• builds an encrypted game.epsa archive from the game data and runtime files,
• decompiles a base APK template,
• customizes the app identity (package name, app name, icon),
• injects the packaged game into the APK assets,
• rebuilds, aligns, and signs the APK.

This means the first iteration in Pokémon Studio does not need to reimplement Android packaging logic in TypeScript. Instead, it should provide a clear and consistent user flow to collect the required inputs, trigger the existing Android export process, surface logs and errors, and expose the generated APK to the user.

The current build flow in Pokémon Studio (create version → configure options → run build → view logs → open Release folder) must therefore be extended to support Android as a target platform, with Android-specific parameters and validations. A later v2 can move this logic into Pokémon Studio itself for better portability and maintainability.

Acceptance Criteria

• The user can select Android as a target platform when creating a build
• The Android option is clearly visible and understandable in the UI, with a dedicated Figma proposal
• When Android is selected, the build form exposes Android-specific fields
• The Android flow clearly distinguishes required inputs from optional inputs
• Pokémon Studio triggers the existing export_android.rb flow instead of a new TypeScript implementation
• The build process generates an APK file as output
• The generated APK is placed in a predictable output location accessible from the existing post-build flow
• Android export logs are displayed in the existing build log window
• Errors returned by the Android export flow are surfaced clearly to the user
• The overall Android build experience remains consistent with the current desktop build flow, without major UX disruption
• The scope of this ticket is limited to integrating the existing PSDK-side Android export process into Pokémon Studio v1

References

• PSDK Android export script: export_android.rb
• PSDK-Android: https://github.com/Scorbutics/PSDK-android?tab=readme-ov-file