Page not found .... page

[macfarlandian]

Description of the change

Any URL that can't be resolved should now land you on a proper "not found" page.

In cases where we can partially resolve the URL (i.e., the tenant is valid but something after it is not), the tenant-specific navigation should be present to give you more recovery paths. This involved changing how we handle invalid route parameters so they don't throw errors ... there is some wonky stuff associated with that but I tried to keep it all encapsulated in the withRouteSync function. It is also complicated somewhat by a bug in Reach Router that obliterates all the route parameters on default routes, so I had to use a wildcard path instead.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Configuration change (adjusts configuration to achieve some end related to functionality, development, performance, or security)

Related issues

Closes #361

Checklists

Development

These boxes should be checked by the submitter prior to merging:

• Manual testing against realistic data has been performed locally

Code review

These boxes should be checked by reviewers prior to merging:

• This pull request has a descriptive title and information useful to a reviewer
• This pull request has been moved out of a Draft state, has no "Work In Progress" label, and has assigned reviewers
• Potential security implications or infrastructural changes have been considered, if relevant

[coveralls]

Pull Request Test Coverage Report for Build 663021110

• 21 of 21 (100.0%) changed or added relevant lines in 7 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.2%) to 73.423%

---

Totals
Change from base Build 662889023:	0.2%
Covered Lines:	2691
Relevant Lines:	3559

---

💛 - Coveralls