chore(router): replace react-router-dom v6 with react-router-dom-v5-compat

[aptmac]

Welcome to Cryostat! 👋

Before contributing, make sure you have:

• Read the contributing guidelines
• Linked a relevant issue which this PR resolves
• Linked any other relevant issues, PR's, or documentation, if any
• Resolved all conflicts, if any
• Rebased your branch PR on top of the latest upstream main branch
• Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
• Signed all commits using a GPG signature

To recreate commits with GPG signature git fetch upstream && git rebase --force --gpg-sign upstream/main

---

Fixes: #1528

Description of the change:

This change replaces the current react-router-dom dependency (and its imports) with react-router-dom-v5-compat

Motivation for the change:

The react-router-dom-v5-compat pack contains the APIs for both v5 and v6 of the router, so no functional changes are required. This change is necessary for the Console Plugin, which only has react-router-dom v5.3.x and react-router-dom-v5-compat v6.11.2 as shared modules. This change allows for the pages that contain useNavigate to render without errors in the Console.

As mentioned in the issue I've linked, there is (were) intentions to update the Console to provide react-router v6 to dynamic plugins, and when that time comes this PR can just be undone.

[andrewazores]

Needs rebasing, and unit tests need to be updated since there is some interaction between Jest and the router module. But looks good otherwise.

[aptmac]

The tests were running fine locally, but in the CI complained of not being able to find 'react-router-dom'. Adding it back at v5.3.x similar to how the console frontend has it looks to have done the trick: b103623#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519R116

[andrewazores]

Seems strange. I wonder if that means that somewhere there's a transitive dependency on a react-router-dom component that the test harness is trying to load, and if we can instead add another jest mock/stub or requireActual to force it to only use the compat version instead?

[aptmac]

I'm wondering now if maybe it's my own setup is doing funny things..

Re-reading the v5-compat instructions it mentions to run it in parallel with v5, and it's package.json has a peer dependency on either v4 or v5 of react-router-dom.