Publish final `pfsConfig` and `pfsDesign` FITS files, before taking sps/fps/mcs/agcc exposures.

Before running any sps/fps/agcc/mcs command which might take an exposure, make sure the current config has been constructed and published. 

Iterate over `sps.lightSources`, and gather the appropriate `fps.pfsConfig`, `sunss.pointing` and `dcb.bundles` values. When any of those values change, trigger the generation of a new, possibly aggregated, `pfsDesign/pfsConfig`.
 
Put published FITS files in `/data/raw/$date/{pfsDesign,pfsConfig}/` – these will be copied with the raw data. We want one `pfsConfig` file for each `visit0`, not one per visit.
 
To highlight the most important configuration: when the `pfi` is the only light source, simply copy/link the `pfDesign` file from the targeting/planning software and the `pfsConfig` from the `fpsActor` output.