Increase no_data timeout for concourse disk check
Increase no_data timeout for concourse disk check

It can take up to 30 mins to re-deploy concourse (because of lengthly
compilation phase). Don't alert if we don't receive metric for that long.

Once we migrate to paas-bootstrap deployed concourse, we can drop this check
completely, as concourse will be deployed by BOSH like other jobs, meaning
it would have same stemcell disk usage.

Currently this check exists to set different thresholds, because bosh-init
puts compilation cache on stemcell disk, which is only 3G image with 1.5G
space left before bosh init uses another 1G. So thresholds for this check
are set quite high to cover that there is only about .5G space available
usually. That will not be case any more when deployed by BOSH...

alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf,alphagov/paas-cf