[WIP] UI memory router refactoring

[MarcMcIntosh]

Backup of smallcloudai/refact-chat-js#323

Add routing library

Description

The pagesSlice / feature / component level routing has started to become a liability, this branch investigates on replacing it with an in memory router so that paths can be used to render pages.

Vscode currently occupies the native navigation, so a in memory solution had to be selected.

There's a fair amount of work to do with replacing the current navigation paths.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactoring (no functional changes, only code improvements)
• Documentation update

How to Test

• Step 1:
• Step 2:
• ...

Screenshots (if applicable)

Checklist

• My code follows the code style of this project.
• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.
• I have updated the documentation where necessary.

Linked Issues

https://refact.fibery.io/Software_Development/UI-chat-js-133#Task/TBD-SPIKE-normalise-navigation-453
https://refact.fibery.io/Software_Development/UI-chat-js-133#Task/SPIKE-Routing-804

Additional Notes