Update process and configuration document identifiers to use component names
[pdune] Update process and configuration document identifiers to use component names
a. This means replacing strings like "BoardReader_np04-srv-011_1234" with strings like "cob0_rce1" (or even better choices).
b. To be completely faithful to what users see in the JCOP Run Control interface, we may need to ask for those strings to be passed from JCOP to DAQInterface, and then down to the artdaq processes.
c. The components names should be used to identify FHiCL configuration documents everywhere (run_records directory, inside the raw data ROOT file, in the artdaq_database configuration archive, etc.)
d. The component names should also be used in all metric reporting, and the substitution of the component name in the metric name should be done in the code. The FHiCL configuration documents could have placeholder substrings that are then replaced with the component names (e.g. <Component>.data_rate would become cob0_rce1.data_rate or EventBuilder001.data_rate).
e. Identifiers for Event Builders, DataLoggers, and Dispatchers should also use component names (or "logical names" if people are not comfortable calling these component names).
f. We should talk about whether we want the process names when we run "ps" to show the component/logical names or not.