New param for XH.reloadApp() to remove query params

[Ryanseanlee]

Hoist P/R Checklist

Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

• Caught up with develop branch as of last change.
• Added CHANGELOG entry, or determined not required.
• Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
• Updated doc comments / prop-types, or determined not required.
• Reviewed and tested on Mobile, or determined not required.
• Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

[amcclain]

We want to call this from the AppContainerModel code that is reloading the page when there is an exception requiring a reload - that's the main case I wanted to catch.

In that use case, we are not spec'ing a path - we want to reload at the current location. We would need to call this as reloadApp(null, true) which is OK but a little sub-optimal.

How about we change the signature to accept a single arg that is either a string - the path, for backwards compatibility - or an object with optional keys path and removeQueryParams:

reloadApp(opts?: string | {path?: string; removeQueryParams?: boolean})

That way if we need to add a new option in the future, we can do so without making more breaking changes. And for the refresh after exception requiring reload, we can call as reloadApp({removeQueryParams: true})