ci: sanitize Android UI workflow logs and remove column flavors (WPB-27951)

[emmaoke-w]

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

…27951)

---

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?

• Sanitize Android UI workflow logs so GitHub only shows high-level failure reasons instead of full instrumentation stack traces and selector details.
• Scope flavor S3 resolution more tightly by passing the resolved S3_FOLDER only to the APK download step instead of keeping it job-wide.
• Fix retry handling so zero-test rerun shards no longer fail the workflow, while still failing the initial run when a selector matches no tests.
• Remove unused column flavor cleanup/install references from the runner-driven CI setup.

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 52.74%. Comparing base (4262323) to head (d71416c).
⚠️ Report is 5 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #5174      +/-   ##
===========================================
- Coverage    52.75%   52.74%   -0.01%     
===========================================
  Files          659      659              
  Lines        23599    23618      +19     
  Branches      3883     3886       +3     
===========================================
+ Hits         12450    12458       +8     
- Misses       10001    10010       +9     
- Partials      1148     1150       +2     

see 4 files with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

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

🚀 New features to boost your workflow:

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

[github-actions]

Test Results

2 243 tests  ±0   2 243 ✅ ±0   2m 11s ⏱️ +30s
  245 suites ±0       0 💤 ±0 
  245 files   ±0       0 ❌ ±0 

Results for commit d71416c. ± Comparison against base commit fdf7a65.

[github-actions]

APKs built during tests are available here. Scroll down to Artifacts!

[yamilmedina]

I don't think this is the right approach, while it might work in my opinion is too crafted/custom.
In practice this can be achieved by changing the LogLevel at WireTestLogger so we have less noise naturally or in AllureLogcatRule (which seems unused) by adding filters.

My point I guess is we are going to miss info, and logs don't harm/specially in testing; it is more an after processing/filtering concern, not about trimming the raw output.

[yamilmedina]

An option is to have this script, but run it manually on demand/locally to filter out noise, but not in the gh output.