chore: sharding tests with 2 simulators for UITests as default - WPB-25757

[findms]

Issue

Please describe the issue.

Optional: add details about technical approach, solutions etc.

Optional: reference dependencies to other pull requests etc.

Testing

Describe how to test.

Optional: attachments like images, videos, etc.

---

Checklist

• Title contains a reference JIRA issue number like [WPB-XXX].
• Description is filled and free of optional paragraphs.
• Adds/updates automated tests.

---

UI accessibility checklist

If your PR includes UI changes, please utilize this checklist:

• Make sure you use the API for UI elements that support large fonts.
• All colors are taken from WireDesign.ColorTheme or constructed using WireDesign.BaseColorPalette.
• New UI elements have Accessibility strings for VoiceOver.

[github-actions]

Test Results

62 tests   51 ✅  1h 3m 4s ⏱️
19 suites   0 💤
 2 files    11 ❌

For more details on these failures, see this check.

Results for commit 5dc0ee3.

♻️ This comment has been updated with latest results.

Summary: workflow run #27126917781
Allure report (download zip): html-report-898-chore_uitest-sharding

[datadog-wireapp]

✨ Fix all issues with Cursor

⚠️ Warnings

🧪 1 Test failed

testAccountManagementLockWithPasscode_TC_8950 from WireUITests.AccountManagementTests     (Fix with Cursor)

failed: caught error: "notLoaded(WireUITests.ConversationsPage)"

<unknown>:0

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 5dc0ee3 | Docs | Give us feedback!}

[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

[findms]

Looks like this is not be the best option by sharding and running on multiple simulators as it makes the CPU reaches 100% which leads to test failure due to slowness as page doesn't load.
Attempting by separating critical tests and regression separately in running to avoid this long running time.
#4823