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.
What's the benefit of unregistering them first?