should we support tslint@next ?

[bhovhannes]

This issue has been created to continue discussion opened at pull request #55, which tried to fix issue #53 .

In order to keep master branch clean all changes from PR #55 were moved into new dev branch.

If we decided to have 2 release channels, stable channel will be published from master branch and unstable (potentially) dev channel will be published from dev branch.
If we decided to have 1 release channel and support both stable and *-dev versions of tslint, we can just merge that dev branch into master.
If we decided to support only stable versions of tslint, we can just delete that dev branch.

[Strate]

As far as I understood from previous conversation, we do not want to get unstable version of tslint while installing tslint-loader with npm2. If this is the main reason, we could remove peerDependency of tslint at all, and force user to install preferred version of linter.