Disable automatic reboots for transition-logs

Automatic reboots on a transition-logs node may interrupt log
processing. Continue to manage reboots for these machines manually.

@jennyd explains why automatic reboots may cause an issue for
`transition-logs`:

> If the logs [processing
> script](https://github.com/alphagov/ci-puppet/blob/17af91244d793410e940a0781841a31b27cdd99c/modules/ci_environment/files/process_transition_logs.sh)
> is interrupted between starting to [process
> logs](https://github.com/alphagov/ci-puppet/blob/master/modules/ci_environment/files/process_transition_logs.sh#L38)
> and [committing the
> results](https://github.com/alphagov/ci-puppet/blob/master/modules/ci_environment/files/process_transition_logs.sh#L51)
> then it will [exit
> early](https://github.com/alphagov/ci-puppet/blob/master/modules/ci_environment/files/process_transition_logs.sh#L20-L23)
> on the next run, and won't be able to process any more logs until that
> is cleared up.

> In addition, if a logfile is only partially processed, we will end up
> with some duplicated results from it (and inflated hit counts getting
> into Transition) because our processing [appends to a cache
> file](https://github.com/alphagov/pre-transition-stats/blob/abe386e43c82fb08c6f1b8775deca8025e40d006/lib/transition/ingest/awk/common-log.awk#L102)
> which covers a whole day. At that stage it would be very hard to
> identify which lines in the cache file came from the partially
> processed logfile. Since our logfiles are rotated hourly, the possible
> impact of that is limited, but it's not ideal.