Register browse routes on deploy

Run the router:register_browse task as part of the router:register task
which gets called automatically on deploy.

Also register redirects for `/business` and `/visas-immigration` on deploy. These will eventually be added to router-data and removed from here, but to make the deployment simpler, we're going to enforce these as part of Collection's route registration for now.
They are different routes. If we were to register the new redirects before unregistering the old ones, there would be potential for redirect loops.

In this case, we:
1. unregister the `/browse/business` and `/browse/visas-immigration` redirects. At this point, any users who request one of these pages will see a browse page served by the existing prefix route (defined in both frontend and collections) rather than a redirect.
2. register the new redirects at `/business` and `/visas-immigration` so that users requesting the old browse routes will get redirected