When using the CLI, if the message is invalid we lose all its content (using a custom message in VIM mode), which might be a little frustrating when we a have a long commit body.

This feature prints the full message when there are linting errors.

Closes #222

### 1. Summary

Fix installation syntax for Windows.

Curly braces syntax [**doesn't work**](https://stackoverflow.com/a/38876970/5951529) for Windows-specific terminals.

### 2. Behavior before pull request

```node
D:\SashaDemoRepositories\SashaCommitlint>npm install --save-dev @commitlint/{config-conventional,cli}
npm ERR! code ENOLOCAL
npm ERR! Could not install from "@commitlint\{config-conventional,cli}" as it does not contain a package.json file.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\SashaChernykh\AppData\Roaming\npm-cache\_logs\2018-04-10T13_23_19_766Z-debug.log
```

### 3. Behavior after pull request

```node
D:\SashaDemoRepositories\SashaCommitlint>npm install --save-dev @commitlint/config-conventional @commitlint/cli

+ @commitlint/[email protected]
+ @commitlint/[email protected]
added 170 packages from 61 contributors in 34.977s
```

### 4. Testing environment

+ Windows 10 Enterprise LTSB 64-bit EN,
+ Node.js 9.11.1,
+ npm 5.8.0,
+ [**Clink**](https://mridgers.github.io/clink/) 0.4.8.

Thanks.

As per issue #307 port the logic from subject-case for array definitions over to scope-case and type-case.

The `npm install` part referenced the wrong list of packages.