The `-reschedule` flag stops allocations and assumes the Nomad scheduler
will create new allocations to replace them. But this is only true for
service jobs.

Restarting non-service jobs with the `-reschedule` flag causes the
command to loop forever waiting for the allocations to be replaced,
which never happens.

Allocations for system jobs may be replaced by triggering an evaluation
after each stop to cause the reconciler to run again.

Batch and sysbatch jobs should not be allowed to be rescheduled as they
are expected to run to completion unless stopped.

Batch jobs are able to be rescheduled without further steps, but
sysbatch jobs never receive a replacement allocation so they are still
not allowed to be rescheduled.