Upgrade console and my account to React Router v6

[pavinduLakshan]

Purpose

$subject

Related Issues

• N/A

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified.
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Ran FindSecurityBugs plugin and verified report?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

[pavinduLakshan]

Kept in draft state since the console refactoring is still going on.

[pavinduLakshan]

Unfortunately, there is no standard way to navigate outside react components since in v6, the direct use of history object is discouraged and react router also doesn't provide a way to implement this functionality[1].

This severely affect migrating our console app to v6, since the features use a shared history and now that is no longer possible out-of-the-box in RRV6 it seems :(.

[1] remix-run/react-router#9422

[wso2-jenkins-bot]

⚠️ No Changeset found

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go.

If these changes should result in a version bump, you need to add a changeset.

Refer Release Documentation to learn how to add a changeset.