Support JSON Schema in Config 

JSON Schema ([schema core](http://json-schema.org/latest/json-schema-core.html), and the [supported keys](http://json-schema.org/latest/json-schema-validation.html))

It will look like this:

```coffee
@config:
  fontSize:
    type: 'integer'
    default: 16
  lineHeight:
    type: 'number'
    default: 1.3
  someArray:
    type: 'array'
    default: ['ok', 'yeah']
    items:
      type: 'string'
  invisibles:
    type: 'object'
    properties:
      eol:
        type: 'string'
        default: '\u00ac'
      space:
        type: 'string'
        default: '\u00b7'
```

### Notes

* If a value is passed to `::set` cannot be coerced, it will not be set (eg. passing `'omg'` to an integer type)

### TODO

* [x] support some of the fancy bits of the schema (minimum, maximum, enum)
* [x] deprecate the `getInt` style methods
* [x] use in our internal classes
* [x] read schema from loaded packages
* [ ] figure out a reasonable notification when there are issues loading user's config
* [x] deprecate `configDefaults`
* [x] write a doc about it I can point to
* [ ] write good docs into Config class
* [ ] convert a package to use schema
* [ ] make sure settings view works
* [ ] maybe remove deprecated calls from settings view
What do you think about moving the defaults out of the views and into the models themselves or just have a `config-defaults.coffee` file that sets all the core/editor defaults in one place?

I always forget that the `core` defaults are in `WorkspaceView` and usually look a few other places first.