Remove "is_job_array" argument to bb_g_job_validate2() function.
Defer starting job that needs persistent burst buffer until it has been created.
Avoid trying to create persistent burst buffer with duplicate name

This will be needed for TRES limit enforcement

This is a more thorough treatment of bug 1790 and commit
  d2545ca746ea0a2f9653664a601052cfd5eb8ad
  It clears the task_id_bitmap once the last task is scheduled
  and task_cnt becomes zero

Prevent job array task ID from being reported as NO_VAL if last task in the
  array gets requeued. The problem is that when that task starts, the task
  bitmap entry for it stays set, but the task counter gets decremented.
  If that job then gets requeued, under some conditions a failure to schedule
  it results in the array_task_id in the job record getting set to NO_VAL.
  Then when building the job info to report for squeue/scontrol, the string
  showing the pending task ID's is not rebuilt due to that counter being
  zero. All indications are that the job runs fine, only the information
  reported to squeue/scontrol is wrong.
bug 1790

accounting correctly to avoid meaningless errors about overflow.

Conflicts:
	config.h.in
	src/sreport/job_reports.c

Bug 1873

Fix shutdown race condition that could cause the plugin to deadlock.
Improve validation of burst buffer options.
Hold job with an burst_buffer specification later discovered to be bad.

intended for the head of the tree.

Handle out-of-band (i.e. outside of Slurm) persistent burst buffer
  creation/deletion with respect to their reservations, as used
  for limit enforcement.

Avoid creating a duplicate burst buffer record due to a race condition
between the "create_persistent" thread and the "load_state" thread.

Improve precisions of poll timeout logic

or binary.

Previously we reported an underflow of the node's comp_job_cnt
  (actually the message reported an underflow of the run_job_cnt,
  but was really checking the value of comp_job_cnt, in any case,
  the count is cleared when the node goes down as we are not
  counting on getting any responses from the down node).

Major refactoring of burst buffer option parsing for interactive
  job support

The --bbf option reads the job's burst buffer options from a file
rather than an inline option

meaning meaning the limit is removed.

wouldn't get the correct protocol version to launch a step.

wait for job TRES limit check before starting burst buffer allocation