Fix confusing debug output about current deploy

Make it clear whether there was or was not a current deployment found.
Don't report supervisor "status" msg as unknown

Its not used, but it isn't unknown or unexpected.
run: improve log messages about actions and state
Fix deploy after current app is stopped

Deploy was assuming that if there was a current app, it was running/had
a child supervisor. This isn't true of the current app has been stopped.
Merge pull request #83 from strongloop/feature/arc-pm

fix deploy after stop
test: refactor docker e2e test script
locked mode: reject all deployment attempts

Respond to all deployment attempts of any kind with a 403 Forbidden
when the STRONG_PM_LOCKED environment variable is set to any non-blank
value.

This feature is primarily for strongloop/strong-arc#656, so the feature
is intentionally undocumented until we decide if/how we want to surface
it in a maintainable way.
v1.4.1
Merge branch 'release/1.4.1' into production
Merge tag 'v1.4.1'

1.4.1

 * locked mode: reject all deployment attempts (Ryan Graham)

 * test: refactor docker e2e test script (Ryan Graham)

 * Fix deploy after current app is stopped (Sam Roberts)

 * run: improve log messages about actions and state (Sam Roberts)

 * Don't report supervisor "status" msg as unknown (Sam Roberts)

 * Fix confusing debug output about current deploy (Sam Roberts)

 * package: use debug v2.x in all strongloop deps (Sam Roberts)
debug: log the info that triggered an update
debug: fix debug output suggesting process leaks

On success, when the supervisor exits, any of its children are updated
in case they weren't previously marked stopped. If they were previously
marked stopped, the usual case, for every ServiceProcess, the following
message would be printed (in debug mode). Under some conditions, this
would be true, but if the process was found, and the stopTime was
already set, this message was wrong and misleading.

    strong-pm:server Got exit event for an unknown process: {"cmd":"exit",...

Fix strongloop-internal/scrum-nodeops#226
debug: don't warn on absence of config file
debug: don't put process.env into the commits

It makes the debug log unreadably long. Instead, merge the commit.env
into process.env just before running.
Merge pull request #84 from strongloop/feature/fix-debug-logging

Fix debug logging
Add Dockerfile for Docker Hub automated build
v1.4.2
Merge branch 'release/1.4.2' into production
Merge tag 'v1.4.2'

1.4.2

 * Add Dockerfile for Docker Hub automated build (Ryan Graham)

 * debug: don't put process.env into the commits (Sam Roberts)

 * debug: don't warn on absence of config file (Sam Roberts)

 * debug: fix debug output suggesting process leaks (Sam Roberts)

 * debug: log the info that triggered an update (Sam Roberts)
Support sl-run spawn on Windows

We were injecting all our dependencies .bin dirs into our path, and
expecting spawn would find them. On Windows, node scripts aren't
executable, so it doesn't matter if they are in the PATH. So, we
tokenize the start command, naively, but good enough for now
(configurability of the start command is going away ASAP), and spawn
node to execute the supervisor script.