The dbd may need to send informaion back right after it registers
(e.g. federation state).

The update could be from a controller registering which wouldn't have
the fed_name set yet.

This reverts commit b7dc369a7fea7caf18ed3515b77f68395056eb99.

rpc_version -> protocol_version

e.g.
sacctmgr modify federation <fed> set clusters=

ex.
sacctmgr add cluster <cluster(s)> federation=<fed_name>
sacctmgr modify cluster <cluster(s)> federation=<fed_name>
sacctmgr add federation clusters=<federation_names>

Goes on the cluster instead.

Problem introduced in commit 0a4d5770

NOTE: Runaway jobs are jobs that don't exist in the controller but are still considered running in the datbase
Should be
NOTE: Runaway jobs are jobs that don't exist in the controller but are still considered running in the database

# Conflicts:
#	src/plugins/jobcomp/elasticsearch/jobcomp_elasticsearch.c

(difference between start of job and when it was eligible).

match that of other plugins.  Send in a pointer to a structure that gets
allocated and then filled in instead of sending in an already
allocation structure.

Had chance to work on DW testbed and fix problems discovered.