If a CO Person with no CO Person Roles, and whose Org Identity is not registered in any other CO, attempts to login to Registry, the user will get stuck in a loop. Lacking any roles, the person will not have permission to render the default Dashboard, which will redirect the user back to /. However, we now try to redirect a user with only one CO to the dashboard rather than the CO picker, so the browser gets stuck in a loop.

In general, if there is an error with CoDashboardController, the user should get directed to somewhere other than /. (And maybe more generally, the default landing point on error should be /pages/error or similar, rather than /.)