ci: configure ci upgrade test flow (WPB-25526)

[emmaoke-w]

https://wearezeta.atlassian.net/browse/WPB-25526

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

• Adds CI support for upgrade test runs using old and new APKs.
• Pushes both old and new APKs to connected devices during upgrade runs.
• Auto-selects the previous APK as the old build when oldBuildNumber is empty.
• Adds excludeCategory runner support so normal phases can skip upgrade tests.
• Runs normal tests first on the new APK while excluding tests tagged upgrade.
• Runs upgrade tests separately afterward, starting from the old APK.
• Keeps retry and manual deflake support working across normal and upgrade phases.
• Logs selected old and new APK names during CI setup and cleans pushed APK files after the run.

Issues

Briefly describe the issue you have solved or implemented with this pull request. If the PR contains multiple issues, use a bullet list.

Causes (Optional)

Briefly describe the causes behind the issues. This could be helpful to understand the adopted solutions behind some nasty bugs or complex issues.

Solutions

Briefly describe the solutions you have implemented for the issues explained above.

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

Needs releases with:

• GitHub link to other pull request

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)

---

PR Post Submission Checklist for internal contributors (Optional)

• Wire's Github Workflow has automatically linked the PR to a JIRA issue

---

PR Post Merge Checklist for internal contributors

• If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.16%. Comparing base (9bbf44c) to head (69b1ed5).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4809      +/-   ##
===========================================
- Coverage    51.17%   51.16%   -0.01%     
===========================================
  Files          611      611              
  Lines        21137    21139       +2     
  Branches      3398     3399       +1     
===========================================
  Hits         10816    10816              
- Misses        9306     9308       +2     
  Partials      1015     1015              

see 3 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9bbf44c...69b1ed5. Read the comment docs.

🚀 New features to boost your workflow:

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

[yamilmedina]

looks good to me! just small changes to improve understanding for future manteiners.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud