fix(unit): enhance selenium retry logic and verification for search, sent, unread, contacts, and history pages

[Shadow243]

ref #1719 (comment)

This fix bridges the gap between modern Single Page Application navigation patterns and traditional browser automation tools

[Shadow243]

@kroky This is now ready for review.

The Selenium test suite was experiencing intermittent failures due to navigation timing issues. The core problem was a mismatch between:

• Modern SPA Navigation: Cypht uses fetch() API with DOM replacement for seamless page transitions
• Traditional Selenium Detection: Tests were expecting classic browser navigation events (load, beforeunload, etc.)

This resulted in:

• Tests proceeding before navigation completion
• wait_for_navigation_to_complete() timing out or returning prematurely
• Inconsistent test results, especially with slower networks or complex pages

We added comprehensive navigation state management in navigation.js

// Navigation state tracking
document.body.setAttribute('data-navigation-state', 'loading|complete|error');

// Custom events for precise detection
window.dispatchEvent(new CustomEvent('navigation-started'));
window.dispatchEvent(new CustomEvent('navigation-completed'));
window.dispatchEvent(new CustomEvent('navigation-failed'));

and upgraded wait_for_navigation_to_complete() with three detection methods:

• Primary: Monitor data-navigation-state attribute changes
• Fallback 1: Detect fetch requests in performance timeline
• Fallback 2: Traditional loading indicator + DOM element detection

Please take a look and give us a feedback about our approach.

[kroky]

Yes, this sounds like the right approach to me. I'll merge and see how it behaves on different PRs. Thanks a lot!

[kroky]

However, the pipeline still fails. Can you make sure to run it several times after you push your fixes and mark it for review?