More flexible release upload with deploy_project.sh

[realkosty]

This is preparation for generalizing this logic and merging this and all other mobile repos into the empower monorepo where we will have a fully automated CI.

Changes:

• parametrize deploy_project.sh with build type (release/debug) and output file name (name under which build artifact will be uploaded to GH)
• if release already exists upload files to it, replacing if a file already exists
• do not mark new releases as "Latest" (will be reserved for master only so it shows up at the top)
• don't build both release and debug, just one

Idea is to have the just 1 latest release, likely named after the master/main branch with artifacts filenames following <project>_[<os>]_[debug|release].<ext> format, e.g:

Release name: master
Tag: master
Timestamp: May 28, 2025
Latest: yes
Artifacts:
- android_release.apk
- ios_release.zip
- react-native_android_release.apk
- react-native_ios_release.zip
- flutter_android_release.apk

Release name: my-pr-branch
Tag: my-pr-branch
Timestamp: Jun 12, 2025
Latest: no
Artifacts:
- ios_release.zip

This will simplify things a lot. Semver releases will still be created in Sentry and baked into application bundles, we just won't be creating GitHub releases for each one.

Testing

ran deploy_project.sh locally

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base (c211625) to head (666ff7a).

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #180   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files         15      15           
  Lines        780     780           
  Branches      43      43           
=====================================
  Misses       780     780           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.