/status endpoint should return 503 Service Unavailable if Stash can't serve traffic (hasn't finished repartitioning, is reaching resource limits, ...)

When Stash:

1. has started but repartitioning hasn't finished running yet, or
2. is queuing requests (either hosting or command tickets are maxed out),

then the /status endpoint should probably return 503 Service Unavailable. This would tell most load balancers to direct traffic to a different node.