Enable setting navigation options with m.route.link API

[orbitbot]

Description

Some refactoring to enable passing the options object to m.route.set using the m.route.link API in lifecycle methods.

Motivation and Context

With current functionality, there is no way to overwrite browser history entries and pass specific parameters to the history API with m.route.link, this always requires a custom method to be written.

Related issues #1807 #1810

How Has This Been Tested?

npm t with new test case.

Types of changes

• 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 change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated docs/change-log.md

[tivac]

🎉

[orbitbot]

Anyone mind processing this? :)

[dead-claudia]

@orbitbot Add a changelog entry, and it'll be ready to merge.

[dead-claudia]

Apologies for this slipping through the cracks... 😟

[orbitbot]

@isiahmeadows What's the proper heading to put a new change-log.md entry under? Is there going to be a 1.1.6, or should I just chuck a line somewhere in the 2.0.0 WIP section?

[dead-claudia]

Just chuck it into the v2.0.0 section - it'll get moved if/once it's backported.

[orbitbot]

Updated the PR.