the jobid string. Reuse the existing job_step_kill_msg_t structure.

if no other command line options are specified.

This is the infrastructure needed to modify a job array with the
new job array data structures. There will need to be additional
work once the RPC is fleshed out.

Previously would not work properly if a job array to be canceled was partly running and partly pending

This is important for job array modifications. Log the job ID in the job record rather than in the modify request.

For improved support of job arrays

which then kill the job or the job array.

Added SchedulerParameters options of bf_max_job_array_resv to control how
many tasks of a job array should have resources reserved for them.

Modify to work if the bitmap sizes of the job and user specification vary.

This adds a new function job_str_signal() which can be used to
cancel/signal a job array using a single RPC rather than a series
if RPCs, one per job record, which does not work with the new
job array data structure. This new logic is untested.

Partitial fix for new job array data structure

Fix squeue --array/-r option to print individual job array task
records even if then are all in a single job record from slurmctld.

Change un/pack_bit_str() to pack_bit_str_hex(), which has much
better scalability and performance.

set exit code on a failure mode previously ignored

Move the formatting of a job array's task ID string from slurmctld
to the client to reduce system overhead. There is logic in place
to translate the full bitmap into a string, but in the worst case
this can take roughly one minute (e.g. 1-1000000:2,2) so by default
only the first 1024 bytes in the string are set. There is logic in
the code to translate the full string, but commented out.

Fix some anomalies in the main scheduling loop for job arrays
Improve logging in the main scheduling loop for job arrays

Now able to run job arrays based upon the new job array data structure.