Preliminary work to migrate to the new Router API

[danielwiehl]

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our guidelines
• [x] Tests for the changes have been added
• [ ] Docs have been added or updated

PR Type

What kind of change does this PR introduce?

• [ ] Fix
• [ ] Feature
• [ ] Documentation
• [ ] Refactoring (changes that neither fixes a bug nor adds a feature)
• [ ] Performance (changes that improve performance)
• [ ] Test (adding missing tests, refactoring tests; no production code change)
• [ ] Chore (other changes like formatting, updating the license, removal of deprecations, etc)
• [ ] Deps (changes related to updating dependencies)
• [ ] CI (changes to our CI configuration files and scripts)
• [ ] Revert (revert of a previous commit)
• [ ] Release (publish a new release)
• [ ] Other... Please describe:

Does this PR introduce a breaking change?

• [x] Yes
• [ ] No

BREAKING CHANGE: Removing qualifier from params has introduced a breaking change.

The view qualifier has been removed from the view parameters as it is static.

BREAKING CHANGE: Moving navigational state to the view handle has introduced a breaking change.

To migrate, read the navigational view state from the view handle instead of the activated route data: WorkbenchView.state.

BREAKING CHANGE: Removed WorkbenchView.cssClasses property for reading CSS classes. Use WorkbenchView.cssClass for both reading and setting CSS classes instead.

Other information