Link plugin to the sbt organization

[ghost]

This will remove the need to specify the tpolecat-sbt-plugin-releases resolver

see http://www.scala-sbt.org/0.13/docs/Bintray-For-Plugins.html#Linking+your+package+to+the+sbt+organization

[ghost]

And will also allow 4 LOC to be deleted from sbt-catalysts that still have to be duplicated in client projects, eg catalysts project

[tpolecat]

It's a bit more complex because tut is actually two libraries: an sbt plugin, and a runtime that is added to your classpath and resolved via normal mechanisms. So we have to be sure that bit still works.

[ghost]

It's a bit more complex because....

Isn't it always 😉

Seems to work in catalysts (even if the produced product is minimal - http://inthenow.github.io/catalysts/ )

[ghost]

btw - code for generic use

[ghost]

Implemented, tested and works 👍