refactor(cli): get rid of sywac dependency and improve CLI-code tests

Some of our oldest tech-debt there... It'll be good to have this over
with. This will unblock a few small improvements but I figure it's best
to do just the refactor first.

docs/reference/commands.md

@@ -20,7 +20,7 @@ The following option flags can be used with any of the CLI commands:
 
 | Argument | Alias | Type | Description |
 | -------- | ----- | ---- | ----------- |
-  | `--root` | `-r` | string | Override project root directory (defaults to working directory).
+  | `--root` | `-r` | path | Override project root directory (defaults to working directory). Can be absolute or relative to current directory.
   | `--silent` | `-s` | boolean | Suppress log output. Same as setting --logger-type=quiet.
   | `--env` | `-e` | string | The environment (and optionally namespace) to work against.
   | `--logger-type` |  | `quiet` `basic` `fancy` `fullscreen` `json`  | Set logger type. fancy updates log lines in-place when their status changes (e.g. when tasks complete), basic appends a new log line when a log line's status changes, json same as basic, but renders log lines as JSON, quiet suppresses all log output, same as --silent.
@@ -30,6 +30,8 @@ The following option flags can be used with any of the CLI commands:
   | `--yes` | `-y` | boolean | Automatically approve any yes/no prompts during execution.
   | `--force-refresh` |  | boolean | Force refresh of any caches, e.g. cached provider statuses.
   | `--var` |  | array:string | Set a specific variable value, using the format <key>=<value>, e.g. `--var some-key=custom-value`. This will override any value set in your project configuration. You can specify multiple variables by separating with a comma, e.g. `--var key-a=foo,key-b="value with quotes"`.
+  | `--version` | `-v` | boolean | Show the current CLI version.
+  | `--help` | `-h` | boolean | Show help
 
 ### garden build
 
@@ -63,7 +65,7 @@ Examples:
 
 | Argument | Alias | Type | Description |
 | -------- | ----- | ---- | ----------- |
-  | `--force` |  | boolean | Force rebuild of module(s).
+  | `--force` | `-f` | boolean | Force rebuild of module(s).
   | `--watch` | `-w` | boolean | Watch for changes in module(s) and auto-build.
 
 #### Outputs

garden-service/bin/garden

@@ -4,4 +4,5 @@ require("source-map-support").install()
 
 const cli = require("../build/src/cli/cli")
 
-cli.run()
+// tslint:disable-next-line: no-floating-promises
+cli.runCli()

garden-service/bin/garden-debug

@@ -4,4 +4,5 @@ require("source-map-support").install()
 
 const cli = require("../build/src/cli/cli")
 
-cli.run()
+// tslint:disable-next-line: no-floating-promises
+cli.runCli()

garden-service/package.json

@@ -117,7 +117,6 @@
     "string-width": "^4.2.0",
     "strip-ansi": "^6.0.0",
     "supertest": "^4.0.2",
-    "sywac": "^1.3.0",
     "tar": "^6.0.2",
     "terminal-link": "^2.1.1",
     "titleize": "^2.1.0",

garden-service/src/analytics/analytics.ts

@@ -20,6 +20,7 @@ import { AnalyticsType } from "./analytics-types"
 import dedent from "dedent"
 import { getGitHubUrl } from "../docs/common"
 import { InternalError } from "../exceptions"
+import { Profile } from "../util/profiling"
 
 const API_KEY = process.env.ANALYTICS_DEV ? SEGMENT_DEV_API_KEY : SEGMENT_PROD_API_KEY
 
@@ -115,6 +116,7 @@ export interface SegmentEvent {
  * @export
  * @class AnalyticsHandler
  */
+@Profile()
 export class AnalyticsHandler {
   private static instance?: AnalyticsHandler
   private segment: any
@@ -443,6 +445,10 @@ export class AnalyticsHandler {
    * @memberof AnalyticsHandler
    */
   async flush() {
+    if (!this.analyticsEnabled()) {
+      return
+    }
+
     // This is to handle an edge case where Segment flushes the events (e.g. at the interval) and
     // Garden exits at roughly the same time. When that happens, `segment.flush()` will return immediately since
     // the event queue is already empty. However, the network request might not have fired and the events are