Ensure routing concerns are moved / kept separate from Fluxity package

## Describe the task

Create extension package that contains functionality to get a display route, and Presenter inherited / extension classes which can operate based on the supplied route, to ensure separation of Fluxity and view/routing concerns.

Binding/Dispatch of routing to extended Presenters should be separate from standard state binding to allow routing to call dispatch without locking dispatch calls.

## Area

Presentation

## Completed When

- [ ] Route state can be interpreted by inheritable/extended Presenter classes
- [ ] Route supports full/partial path alignment
- [ ] Presenters can operate based on route
- [ ] Route dispatching is separate from other State routing (i.e. route is separate from Fluxity State)

## Additional context

### Example
Routing to a feedback page resets / sets initial feedback state
- when the route tells the page to display, the page's display call dispatches a 'Reset feedback form state' command
- dispatched command resets state and feedback form presenter supplies updated state