This improves the packing for a configuration of
topology/tree, dragonfly, select/cons_res when specific nodes
are required.

* Add "TopologyParam" configuration parameter. Optional value of "dragonfly"
  is supported.
* select/linear: Add dragonfly topology support
* select/cons_res: Add dragonfly topology support

We plan to duplicate partially duplicate a function and replaced
that function name in logs with "__func__" for better code re-use.

No changes to the test logic

Conflicts:
	doc/man/man1/sacct.1
	doc/man/man1/srun.1
	src/sacct/sacct.h

Bug 1578

Bug 1550

their own jobs.

Bug 1469

This seems to apply only to Cray/ALPS systems.
This partially reverts commit 5fc68cae
It also adds a new check for NULL job_ptr

_entity_add_data() in src/common/entity.c defined as "static" to avoid
    confusion with same function name in src/common/layouts_mgr.c
_entity_get_node_walkfunc() in src/common/entity.c defined as "static"
Removed redundant set of "rc" variable _layouts_autoupdate_layout_if_allowed(),
    src/common/layouts_mgr.c
Initialized variable "rc" in _layouts_read_state(), src/common/layouts_mgr.c
    in case the named file does not exist (stat() returns an error)
The CLANG tool reported a possible error in _autoupdate_layout_tree(),
    src/common/layouts_mgr.c in the event that xtree_node_get_data()
    returns a NULL value and that pointer is used later in the function for
    "cnode->entity". I added "return 1" if xtree_node_get_data() returns NULL,
    but am not yet sure if that is the correct action.
The CLANG tool reported possible errors related to a NULL value pointer in
    s_p_parse_pair_with_op(), src/common/parse_config.c which have been fixed.

Having MAX_PREFIX_CNT to 1k limits the number of elements that can be
expressed using expressions like node[1-1025].ib[0] to 1024.

As 64k is the max number of nodes that can be handled by Slurm, increase
that value to 64k in order to be able to express at least that number of
elements using a[x]b[y] when y is the same value for all the elements.

Note: also required by the layouts parsing logic when parsing float values
in expressions like : 'Entity=node[1-64000] FloatKey=[1-64000].[0]'