test: group video call critical flow test (WPB-22855)

[emmaoke-w]

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

---

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?

• Added GroupVideoCall critical-flow test that covers full group video call behavior: backend setup, cross-team connection, participant add, call start/join, camera/video on, participant visibility, ping confirmation, in-call audio-recording restriction, audio-file playback checks, and call end.
• Added/extended page-object methods needed by this scenario (group conversation details participant actions, group conversation details open, ping modal actions, call controls like camera on/restore/hang up, and audio modal handling).
• Expanded call support helpers to validate group-video participants and stronger audio/video receive checks for all call participants.
• Updated test-service helpers for more reliable conversation/message handling, strict personal MLS send entrypoint (userSendMessageToPersonalMlsConversation), improved conversation timer lookup (personal/group fallback), and clearer failure reporting on send.
• Updated QR image creation in FileUtils to use MediaStore on Android Q+ (scoped storage safe write to Downloads), with legacy path handling kept for older Android versions.
• Hardened flaky UI interactions with SystemClock-based polling/retry across key flows (notification/consent dialogs, menu/settings click path, modal visibility/disappearance checks, download modal Save click).
• Added reusable wait helpers in UiWaitUtils (waitUntilVisible, waitUntilToastIsDisplayed, iSeeSystemMessage, assertToastDisplayed) and strengthened element stabilization timing.

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.

[pull-request-size]

Ups 🫰🟨

This PR is too big. Please try to break it up into smaller PRs.

[CinnamonNinja]

LGTM!

[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