Add initial jsdoc build process and region api

This is a first pass at setting up a js-doc based api. The PR includes a grunt task and new region jsdoc file.

The grunt task (jsDocFiles) compiles the jsdoc api files to json. This is done by first parsing the yaml file, then iterating over class functions and parsing the jsdoc. I chose to compile to json here because building the html seems like a job for `www`. It's fairly trivial to do and they'll be a basic PR for doing that with Handlebars soon.

The region jsdoc file is a pretty good first pass. I'd appreciate it if you can double check the function signatures. Read over @jmeas' function descriptions. And maybe help add some content + other tweaks as well. Although, with that said, I would like to get this PR in fairly cleanly so that we can move on to adding other api files as well and figure out the appropriate style once we have more examples.

Here's a gist of the json that grunt builds [json](https://gist.github.com/jasonLaster/894b6c8fc56e5696760c0

>  As you might already know, Views render the actual content that you would like to display. But not all Views render content that is attached to the `document`. These views render a detached DOM tree, that isn't visible to the user. This creates a new responsibility attaching that detached tree to another tree. This is what Regions are for they serve as a connector between DOM trees.

hmmm this is weird I would just :x:  it and replace it with something like

Regions are for creating reusable render targets.