Handle async Remix navigation properly

[gbalint]

Problem:
I believe the Remix tests are flaky for 2 reasons:

1. the remix router navigate functions are async, and we just call them with void in the RemixNavigationContext.back/forward/home functions. And these are the function which are called in the mouse event handlers of the remix navigation buttons.

2. In the tests we wait for getDispatchFollowUpActionsFinished, but that doesn't really help, because remix navigation does not trigger a dispatch (but it still triggers a rerender, and we have to wait for that)

Fix:
Since it is really hard to expose the event of finishing of the navigation and the rendering, so I just decided to use the waitFor helper of react testing library, which can wait for a given timeout until an expectation is true.

[github-actions]

Try me

[relativeci]

Job #10245: Bundle Size — 62.35MiB (~-0.01%).

a09bca4(current) vs 794431b master#10224(baseline)

Warning

Bundle contains 66 duplicate packages – View duplicate packages

Bundle metrics   2 changes 1 improvement

	Current Job #10245	Baseline Job #10224
Initial JS	35.39MiB(~-0.01%)	35.39MiB
Initial CSS	0B	0B
Cache Invalidation	20.23%	21.77%
Chunks	28	28
Assets	32	32
Modules	4407	4407
Duplicate Modules	490	490
Duplicate Code	30.7%	30.7%
Packages	462	462
Duplicate Packages	65	65

Bundle size by type   1 change 1 improvement

	Current Job #10245	Baseline Job #10224
JS	62.34MiB	62.34MiB
HTML	11.37KiB (-0.32%)	11.41KiB

---

View job #10245 report View fix/flaky-remix-test-3 branch activity View project dashboard

[github-actions]

Performance test results:
Highlight Regular (-2%)

Highlight All Elements (0%)

Selection (4%)

De-Selection (6%)
Before: 9.9ms (8-16.8ms)
After: 10.5ms (8.3-16.9ms)

Selection Change (2%)

Scroll Canvas (22%)
Before: 3.2ms (2.4-9.7ms)
After: 3.9ms (2.8-8.5ms)

[github-actions]

Performance test results: