fix: results route handling in dev mode

[Chartman123]

This fixes a regression introduced in #3432. When you reloaded a results page with F5 or directly called a subview when the app was running with npm run dev, the results view got duplicated over and over into the router-view.

As a fix/refactoring I moved the routes from url params to direct child routes defined in router.ts.

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI

[codecov]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
lib/Controller/PageController.php	0.00%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!

[pringelmann]

@Chartman123 sorry I was meaning to do a review this morning. I found a bug where switching to different result views contains stale data:

Two things here, both needed:

1. props: { default: true } is on the parent record, which has no components, so it never applies. Move it to both children or the hash prop stays empty forever.
2. The hash watcher only calls fetchFullForm() now. It used to hit loadFormResults() through syncActiveResponseViewFromRoute(). Add it back, the comment above it still says "Reload results when form changes".

Unrelated: the view only gets saved to localStorage from the $route.name watcher, which doesn't fire on mount, so a reloaded /results/responses isn't remembered. Saving in beforeMount fixes it, but that flips your new redirect test to /results/responses.