Refactor URL redirect after login

[williamjallen]

Our current redirect logic is messy, and just happens to work for most CDash systems. For CDash-in-a-subdirectory systems, the redirect logic is somewhat broken.

This PR refactors the entire system to consistently apply redirects to all web routes.

[josephsnyder]

The changes all look good, but don't have an effect on the subpath system as I've set it up. Redirecting to a project page still duplicates the subpath and redirects to / still do not redirect to /projects

[williamjallen]

@josephsnyder are the values of url.intended consistent now at least?

[zackgalbreath]

A bit more context that I recently discovered:

1. Laravel officially does not support deploying to a subpath 😱 [1] [2]

2. Nonetheless, I got the "/" route to work correctly once again for my local bare-metal, CDash-in-a-subpath installation by making the following change to install.sh:

-php artisan route:cache
+php artisan route:clear

[williamjallen]

@zackgalbreath Thanks for digging up that issue! I looks like the issue is specifically with caching of the / route. One option is to simply turn off route caching. Based on my testing a while back, this would probably result in a 2-3% slowdown for every request.

I wonder if this issue is related to the specific configuration you have though. Does clearing your route cache (php artisan route:clear) also fix your system @josephsnyder? Could an Apache RewriteRule be used instead?

[josephsnyder]

I wonder if this issue is related to the specific configuration you have though. Does clearing your route cache (php artisan route:clear) also fix your system @josephsnyder? Could an Apache RewriteRule be used instead?

@williamjallen, it does. Though, further testing finds that running route:cache causes it to stop working 🤷

[williamjallen]

Since the / route issue is independent of these changes, I created a separate PR to remove the route cache altogether: #2276