Make cpu-stop consistent with heap-snapshot

* Pass file path to and save file on the backend.
* Make both commands return the file path of the saved profile data.
* Make errors reported during profiling are printed to console.
package: cluster-control and log-transformer 1.x
run: refactor usage into a text file
Merge pull request #68 from strongloop/feature/refactor-usage

run: refactor usage into a text file
test: delete STRONGLOOP_METRICS after each test

Leaving an invalid STRONGLOOP_METRICS in the environment causes
subsequent tests to fail.
run: directly support statsd backends

For new metrics URL formats, start a statsd child process, and use it to
deliver metrics to (at this moment) splunk, console, graphite, and
syslog.
Expose worker log transformer/wrapper via config
Use --log mechanism for statsd process
run: exit if metrics URL is invalid
Merge pull request #65 from strongloop/feature/statsd

run: directly support statsd backends
v1.1.1
Merge branch 'release/1.1.1' into production
Merge tag '1.1.1'

v1.1.1
test: cpu profiling now works on v0.10

strongloop/strongops#2ba8228b84cfbebd44e103ccb78da676a2c7b40a added cpu
profiling support for v0.10 in strong-agent v1.0.3, so remove the code
dealing with it not being supported on some node versions.
Merge pull request #71 from strongloop/feature/cpu-prof-on-v0.10

test: cpu profiling now works on v0.10
package: strong-agent-statsd is not directly used
metrics: forward internal metrics to parent

Forwarding is fairly transparent. If there is a statsd child, and if it
emits metrics, and if we have an ipc channel to our parent, we notify
the parent of the metrics. Otherwise, we don't.
Merge pull request #70 from strongloop/feature/fe-metrics

fe-metrics
Add IPC notifications for tracking and profiling
metrics: deal with app and host names with a `.`

Do not allow dots in our app or host name substitutions, they mess up
the statsd metrics hierarchy, which uses `.` as a separator.