`init` command in Go.

Open questions

 * How to do the config checking? Do we want to parse the config files in init
 and check for proper values? Or do we want to just check if the files exists
 and yell at user if the config is missing when they invoke a command that uses
 that config?

Change-Id: 5ab51c5e33
Story-Id: 79247470
Inline comment fix.

Change-Id: 7cb5413134
Replaced `Must*` functions by their error returning versions.

Change-Id: 787ed1b271
Multiline strings in ASCII art.

Change-Id: aaa1e85957
Moved invoking shell into a package.

Change-Id: 7d8d2838d4
Make logging consistent with the rest of the app

Change-Id: 2b75af3195
Better error handling.

Distinguish between "fatal errors" and "expected errors".

Change-Id: ddc2b12e1d
`init` command in Go.

Open questions

 * How to do the config checking? Do we want to parse the config files in init
 and check for proper values? Or do we want to just check if the files exists
 and yell at user if the config is missing when they invoke a command that uses
 that config?

Change-Id: 5ab51c5e33
Story-Id: 79247470
Inline comment fix.

Change-Id: 7cb5413134
Replaced `Must*` functions by their error returning versions.

Change-Id: 787ed1b271
Multiline strings in ASCII art.

Change-Id: aaa1e85957
Moved invoking shell into a package.

Change-Id: 7d8d2838d4
Make logging consistent with the rest of the app

Change-Id: 2b75af3195
Better error handling.

Distinguish between "fatal errors" and "expected errors".

Change-Id: ddc2b12e1d
Minor changes to error handling.

Change-Id: b788d93fbb
Merge branch 'go-init-cmd' of github.com:salsita/SalsaFlow into go-init-cmd

Conflicts:
	git-trunk/commands/init/command.go

Change-Id: 816f62198a
Merge pull request #2 from salsita/go-init-cmd

`init` command in Go.