There are two equivalent long-form options. Add a new LONG_OPT_CLUSTER
to the enum to distinguish which form is used. (Needed for tracing at
a later point in time.)

Neither salloc/sbatch reset this. I believe reseting each pass,
as is done by srun, is the correct behavior, otherwise each separate
component will request additional licenses which is unintuitive.

For reset, salloc always reset this where sbatch/srun would not.
Choosing to go with sbatch/srun's behavior.

This should be avoided, but if there are multiple slurm_opt_t entries for
a given val (e.g., -W in sbatch vs srun) check that we've found the correct
entry.

Non-single-character options do not have this issue since they should just
use differing LONG_OPT values.

A number of validation routines - especially within srun -
care whether the variable was set through the environment, or by
an explicit CLI option (or embedded in a job script).

Provide an easy central test so this can be handled for all arguments.

The envvar interface requires some translation to be handled
in the same manner of options returned from getopt_long(),
as it will intentionally return empty strings for certain
variable types.

Match OPT_BOOL processing for flags (defined as has_arg = 0 for
their getopt_long equivalents).

Options will only be printed if set going forward, rather than the
somewhat-arbitrary list of options that we've remembered to add here.

Print each option alongside the value set by slurm_process_option().

Used to create trivial set functions when the argument value is simply
xstrdup()'d into the associated field in slurm_opt_t.

After 426abc7f no jobs should be able to be removed from the
job_list while backfilling is running.

Bug 6621

Timestamps were previously being updated before acquiring mutexes.
Change it to update timestamps after mutexes have been acquired.

Bug 6621

Bug 6621.