Support Android ADI verification APK generation (Google Play Publishing Blocker)

Base44 should support Google Play Android Developer Verification package registration when Play Console asks for a signed APK containing:

adi-registration.properties

inside the Android assets folder.

After the Android Developer Verification rollout, Play Console can require package name registration before an app listing can be created. In some cases, Google asks developers to upload a signed APK containing this verification file.

Currently, Base44 users can generate APK/AAB files, but they cannot modify native Android files or inject custom files into the APK before signing. This can block Google Play publishing completely.

Requested support:

1. Allow build-time injection of required Android files such as assets/adi-registration.properties.

2. Allow users to provide the Google verification token/snippet securely before APK generation.

3. Generate a signed APK specifically for Google Play package name registration.

4. Ensure the APK is signed using the same signing key/certificate used for the app’s Google Play build.

5. Provide clear documentation for this Android Developer Verification flow.

This is not just a convenience feature. It’s a hard blocker for publishing Base44 apps to Google Play. I’d literally stuck from publishing the app despite it being ready a few days ago.