Persisted environment variables for strong-pm hosted applications

 * [x] Create persisted environment on pm start
 * [x] Inject persisted environment into `prepare` and `run` phases
 * [x] Set environment variables via `pmctl env-set K=V [K2=V2...]`
 * [x] Get environment variables via `pmctl env-get [KEYS...]`
 * [x] Unset environment variables via `pmctl env-unset KEYS...`
 * [x] CLI argument parsing/validation
 * [x] Document CLI

Additional functionality for later PR:
 * Expose environment via REST API models as part of service state

Refs: strongloop-internal/scrum-nodeops#99
Doesn't handle 

- set-env K
- set-env =V
- set-env =
- set-env K=

All should throw, I think... or perhaps the empty value is intended, so env-set can be used as env-unset? I'm not sure.