cr publish.sh

Conversion process phase: publish

• The original need (done here) was to step into each conversion cockpit to invoke the extant publication trigger.
• A newer need (done here) is to handle custom publication triggers anywhere within the dataset abstraction hierarchy. e.g. https://github.com/tetherless-world/opendap/blob/master/data/source/us/opendap-prov/version/retrieve.sh#L77 for https://github.com/tetherless-world/opendap/wiki/OPeNDAP-Provenance
• The newest need (done here) was to publish the given files into htdocs and SPARQL endpoint -- a generalization of aggregate-source-rdf.sh for any file type instead of just RDF (they need to get linked into htdocs).

Predecessors to cr-publish.sh:

• bin/convert-aggregate.sh was the original and is only used in the tabular conversion workflow. It is deprecated in favor of cr-publish.sh but is still heavily used and has been kept in sync since deprecation.
• bin/aggregate-source-rdf.sh assumed just rdf input files. bin/cr-publish-cockpit.sh is a wrapper that digs into each conversion cockpit to invoke aggregate-source-rdf.sh.
• bin/cr-ln-to-www-root.sh (See cr ln to www root.sh for more discussion)