Add Debug build to Releases tab

### What is this about?

Developing for MetaMask Mobile is made much easier when developers are able to connect to a dev console, such as by `chrome://inspect/#devices`; this should not be reliant on being able to compile an APK from source

It would be beneficial to have the debug build in the [Releases](https://github.com/MetaMask/metamask-mobile/releases) tab, and/or an `Advanced Settings` toggle for debugging built into the prod version.

### Scenario

Getting to a dev console from MetaMask mobile requires a pretty large amount of resources and time, something that in any major browser takes seconds at most. MetaMask Mobile could make this easier by providing the debug build in the [Releases](https://github.com/MetaMask/metamask-mobile/releases) tab, which would enable developers to just grab the APK even if they're on the go, in a coffee shop, at the airport, or who knows where else, instead of having to set up an entire Android development environment

With access to the dev console, I should now be able to fix an issue that's been sitting in prod for my dApp, which has seemingly only affected MetaMask Mobile users.

After a week or two of fiddling, I finally got MetaMask Mobile to compile into `app-prod-debug.apk`, and installed it onto my Pixel 9. The resulting Ubuntu 24.04.1 VM uses about 40G, with 1.1 left free:
```
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.6G 1.7M 1.6G 1% /run
/dev/sda2 40G 37G 1.1G 98% /
tmpfs 7.9G 73M 7.8G 1% /dev/shm
tmpfs 5.0M 8.0K 5.0M 1% /run/lock
tmpfs 1.6G 160K 1.6G 1% /run/user/1000
```

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start with the Releases tab and the app-prod-debug.apk build output described in the issue. Clarify whether the intended deliverable is a published debug APK, an Advanced Settings toggle, or both, then define the release, security, and review requirements. Done means the agreed debug access path is available to developers and verified on MetaMask Mobile.

Written by the indexing model from the issue text.