Fix for issue #560

Teased apart the show region behavior into its close, render, open behaviors on the view.
Fixed test running issue related to grunt jasmine dependency
Add TextMate settings for the right indentation
Throw with a classname when the template is falsey

Previously if there was no template definition on a View, rendering the view would throw an exception where the last non-Backbone/Marionette function would be at level 17 in the backtrace. This made tracing the view without template a little annoying. Since a boolean check is not that much of a heavyweight (and the render call only occurs twice) we raise before calling Renderer.render() if we find a template that is falsey (undefined, false or null)
Merge the grunt-jasmine patch by KevM

I cannot start the test suite otherwise
Throw on undefined view templates

If a template is undefined, it could bleed very far into the render stack, and the render would fail with "undefined is not a function" which is about as helpful as error messages get. Instead we can do a small boolean check when rendering and if the template turns out to be falsey, just throw without engaging the Renderer at all. The error message is much clearer as well.

Due to the beauty of JavaScript we cannot say from which View class we had to raise, but this is something that's not so easy to address.
Merge remote-tracking branch 'kevm/issue560' into dev
changelog for PR #562
Merge remote-tracking branch 'kevm/grunt-jasmine' into dev
deleted un-needed constructor from ItemView
Merge remote-tracking branch 'julik/throw-meaningful-exceptions-on-missing-templates' into dev
moved error throwing for not found template in to Renderer.render method