Lengthen route registration timeouts
Lengthen route registration timeouts

- bosh-lite CATs was failing sporadically with 404s from
login.snitch.cf-app.com
- investigation showed that UAA's health check was timing out, causing
the route registrar to deregister the routes
- the problem seems to be a timeout race condition of some kind
- the route registrar timeout is half of the registration interval by
default
- the registration interval for uaa is 4s, so the timeout is 2s
- meanwhile, the uaa health check script curls it's health check
endpoint with a connect timeout of 2s and a max timeout of 5s
- neither the UAA team, the routing team, nor the release integration
team knew why 4s was chosen
- other examples show 20s
- so, we are bumping the registration interval to 10s to bring the
timeouts for the uaa health check script and the route registrar more in
line with each other

[#141176075]

Signed-off-by: Ming Xiao <fde61075b779168f6585a9760a4f9e9e08423562@pivotal.io>

emalm/cf-deployment,cloudfoundry/cf-deployment,cloudfoundry/cf-deployment