srm: simply job.setState

There are currently two setState methods in Job.  The two-arg version calls the 3-arg
version will the 'save' argument hard-coded to true.  The 'save' argument provides
some control over whether the updated job is saved to some JobStorage.

Currently, all calls to setState use the 2-arg version (with 'save' as true),
except for Scheduler, which explicitly calls job.saveJob, so has the same
effect as calling the 2-arg version.

This patch simplifies the process by removing the 3-arg signature method
and always calling the zero-arg saveJob method.

Target: master
Patch: http://rb.dcache.org/r/6651/
Acked-by: Gerd Behrmann
Acked-by: Dmitry Litvintsev