Redirect controller / to /api/v1

The controller currently responds with some deployment configuration on the controller's / route. I propose redirecting / to /api/v1 instead so that limits and details specific to the API are served instead.

Start at the controller's / route and trace how it currently serves deployment configuration, then compare it with /api/v1. Done means / redirects to /api/v1 and the API-specific limits and details are served there; add or update a focused route test if the existing test location is found during that review.

Written by the indexing model from the issue text.