feat: Adding ClosableNavigator to close dialog/flyout when attempting to navigate to unsupported route

[nickrandolph]

GitHub Issue (If applicable): closes #1394

PR Type

What kind of change does this PR introduce?

• Feature

What is the current behavior?

No easy way to navigate from inside a dialog/flyout to a route in the main window of the application. This should close the dialog/flyout

What is the new behavior?

If the route can't be navigated to within the dialog (eg the route isn't part of the routemap for the route already open in the dialog/route), the navigation request is forwarded to the navigator that initially opened the dialog/flyout. The Dialog/Flyout is also closed

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)