Take the best concepts from both functions and produce a unified
version so now the list of accepted signal names will stay in sync.

Also fix the comment to note that 0 is returned on failure, not -1.

Bug 4227.

Also modify a log message for better clarity

Previous logic would result in error if Slurm version > 17.11

The problem was the tests set the same variable, opt_arg, for for
options, --test_suite and --test_suite_reg. But with the addition of
de24ce72 the variable was being set with the different numbers out
of order because the variable was being set from the environment. So the
fix is to have the options set their own variable.

Bug 4176

to avoid name collisions with c++ list types. gdb started showing the
wrong type when the full lib was created.

to set -O0 since --enable-developer and --enable-debug set
optimizations.

What appears to have happened is we changed only the non-internal setup.  So
technically this isn't needed, but does help with handling confusion later.

Coverity CID 44977

_alloc_mask() can return NULL, which was not handled.
Coverity CID 44859

Kept separate for clarity.

Bug 4014.

Note: This check is needed since the maximum file path length really
  is file system dependent and not something local to the Linux distro
Coverity CID 45200

Coverity CID 45343

Really should not happen, but this adds checks
Coverity CID 171449

Coverity CID 45167

Coverity CID 44823

Coverity CID 45160

Setting -Werror tricks the test into failing on the

"error: In the GNU C Library, "major" is defined by <sys/sysmacros.h>.
 For historical compatibility, it is  currently defined by <sys/types.h>
 as well, but we plan to remove this soon. To use "major", include
 <sys/sysmacros.h> directly. If you did not intend to use a system-defined
 macro "major", you should undefine it after including <sys/types.h>."

error. Since the normal Slurm build uses -Werror, this warning on including
both headers will then cause the build itself to fail.

Bug 3982.

deadline_time_limit is ensuring this is always set, but the optimizer
appears to not be able to work out the flow here.

Move test above the accounting limit check. Change the test
to verify first_job_ptr instead of pack_job_id to avoid warning
about a possible dereference of an uninitialized variable lower down.
(Note that both pack_job_id and first_job_ptr are set at the same time,
so this test is functionally equivalent but able to convince the compiler
that things will be okay.)

This one's a bit confusing, and should be a false positive, but
initializing the saveptr argument to strtok_r quiets things down.

Treat default case as an error.
Visible with GCC 6.3 and -01.