Logs errors related to apbasil use

No change in logic, just move the logic that resets a batch job
accounting information into its own function.

No change in underlying logic

This fixes a problem where a job contains a license that is removed
in a slurmctld reconfiguration. Without this change, the job would
be left with a non-zero license_list pointer referencing memory that
had been freed
bug 527

Increase the range of possible reservation time values to allow
for a really long RPC delay (possibly due to slurmctld fail over
from primary to backup controller).
Also change to a #define value for clarity
bug 527

This might be useful for debugging, but could be easily induced
by the backfill scheduler or events introducing heavy load on
the messaging system

The time/resource allocation matrix is rebuilt on each job
exit, which severely impacts performance at large counts of
running jobs (say >10k jobs).

bug 511

This makes it simpler to enable detailed debugging for reservations.
This includes more information than we probably want to see with
the DebugFlag=reservation and would be only for developer debugging

This might have worked fine for core reservations or when there
are sufficient idle nodes to use, the the select_g_resv_test()
function clears the node bitmap for nodes that it can not use
and the reservation create logic did not restore that bitmap
after a failed resource selection attempt. This logic restores
the node bitmap on a failed call to select_g_resv_test() so we
can add nodes to the bitmap of available nodes rather than having
it repeatedly cleared.
The logic also adds some performance enhancements that I will
add to in the next commit.

on a task level if any task hit it the check will be triggered)

use mem and memsw failcnt, check for existence

Thanks Ryan.  I'll let you know how it goes.

task/cgroup: notify if memory.memsw.failcnt > 0. indicates oom

Thanks Ryan, this looks correct.

Correction to hostlist parsing bug introduced in v2.6.4 for hostlists with
more than one numeric range in brackets (e.g. rack[0-3]_blade[0-63]").
bug505

Avoid decrementing grp_used_cpu_run_secs if we are not enforcing
accounting limits. Without this change, the plugin will decrement
times from zero cpu used times (i.e decrement an uninitialized
variable).

Add argument to priority plugin's priority_p_reconfig function to note
when the association and QOS used_cpu_run_secs field has been reset.
Without this flag, we remove time on "scontrol setdebug" or
"scontrol setdebugflag" that can result in used_cpu_run_secs
going negative or otherwise get bad values.
Correction to logic added in commit 6d793189
bug 423