refactor(webapp): clarify deterministic time control naming in tests [WPB-23299]

[screendriver]

WPB-23299 [Web] Add support for remote force reload

Pull Request

Summary

Replace "fake wall clock" terminology with "deterministic wall clock" to make the test-time semantics explicit and consistent across the webapp test suite.

---

Security Checklist (required)

• External inputs are validated & sanitized on client and/or server where applicable.
• API responses are validated; unexpected shapes are handled safely (fallbacks or errors).
• No unsafe HTML is rendered; if unavoidable, sanitization is applied and documented where it happens.
• Injection risks (XSS/SQL/command) are prevented via safe APIs and/or escaping.

Accessibility (required)

• I have read and this PR upholds our Accessibility Best Practices.

Standards Acknowledgement (required)

• I have read and this PR upholds our Coding Standards and Tech Radar Choices.

---

Screenshots or demo (if the user interface changed)

Notes for reviewers

• Trade-offs:
• Follow-ups (linked issues):
• Linked PRs (e.g. web-packages):

[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

[github-actions]

🔗 Download Full Report Artifact

🧪 Playwright Test Summary

• ✅ Passed: 10
• ❌ Failed: 0
• ⏭ Skipped: 3
• 🔁 Flaky: 1
• 📊 Total: 14
• ⏱ Total Runtime: 84.0s (~ 1 min 24 sec)

specs/CriticalFlow/conversationManagement-TC-8636.spec.ts (❌ 0 failed, ⚠️ 1 flaky)

• ⚠️ Conversation Management (tags: TC-8636, crit-flow-web)