chore: React Router v7

[Artur-]

No description provided.

[mshabarov]

We can try opt-in the feature flag immediately, i.e. #20527, what do you think? Flow team can take over and try how validation goes.

[mshabarov]

And I propose to target this jump to Vaadin 24.7.

[sonarcloud]

Quality Gate passed

Issues
49 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

[Artur-]

We can try opt-in the feature flag immediately

Aren't all the flags gone in v7 and automatically on?

[github-actions]

Test Results

1 128 files   - 30  1 128 suites   - 30   1h 27m 41s ⏱️ - 2m 47s
7 443 tests  - 70  7 371 ✅  -  89  51 💤  - 2  2 ❌ +2  19 🔥 +19 
7 764 runs   - 90  7 683 ✅  - 109  60 💤  - 2  2 ❌ +2  19 🔥 +19 

For more details on these failures and errors, see this check.

Results for commit 162c089. ± Comparison against base commit 380b15f.

This pull request removes 70 tests.

com.vaadin.flow.BackNavIT(production) ‑ backButtonWorksAndContentUpdatesAfterPageRefresh[any_Chrome_]
com.vaadin.flow.BackNavIT(production) ‑ testBackButtonAfterHistoryStateChange[any_Chrome_]
com.vaadin.flow.BackNavIT(production) ‑ validateNoAfterNavigationForReplaceState[any_Chrome_]
com.vaadin.flow.ForwardTargetIT(production) ‑ testRouterLinkSetParameterCalledOnlyOnceAfterForward[any_Chrome_]
com.vaadin.flow.ForwardTargetIT(production) ‑ testSetParameterCalledOnlyOnceAfterForward[any_Chrome_]
com.vaadin.flow.ForwardTargetIT(production) ‑ testUrlIsCorrectAfterForward[any_Chrome_]
com.vaadin.flow.NavigationIT(production) ‑ testAnchorWithQueryNavigation[any_Chrome_]
com.vaadin.flow.NavigationIT(production) ‑ testNavigatedEvent[any_Chrome_]
com.vaadin.flow.NavigationIT(production) ‑ testNavigatedForPostponeView[any_Chrome_]
com.vaadin.flow.NavigationIT(production) ‑ testNavigationBrowserHistoryBack_anchor[any_Chrome_]
…