Removed scala dependencies from the compiler project

This has to be done because Scala has a real problem around binary incompatibility
of different Scala versions.

Up until now Mustache.java has been lucky enough that the classes it uses were
only deprecated in Scala 2.10 (e.g. [ScalaObject] and [JavaConversions.asJavaMap]).

In Scala 2.11 these interfaces have been removed. In order to support Scala in
the future I propose removing all the Scala code from the compiler project and
creating a separate project that can be published in multiple forms, one for
each of the scala versions that are commonly used. I'd propose Scala 2.9, 2.10
and 2.11.

  [ScalaObject]: http://www.scala-lang.org/api/2.10.4/index.html#scala.ScalaObject
  [JavaConversions.asJavaMap]: http://www.scala-lang.org/api/2.11.1/index.html#scala.collection.JavaConversions$
brought scala extensions for scala-2.8 into it's own package
implemented scala extensions for scala-2.9

Same as scala-extensions-2.8 except for the version of com.twitter.util-core.
The version needed by 2.8 uses scala 2.8 so I've switched this package to a
that uses scala-2.9 to minimise scala version confusion.
applying d40e2eec628064d1a9a83271556cc0bed885263f to new ScalaObjectHandlers
bumping version number since i missed that when rebasing
implemented scala-extensions for scala 2.10

I have removed the TwitterObjectHandler as com.twitter.util-core doesn't have a
published version thats built for Scala 2.10.

com.twitter.util-core.6.12.1 is built for Scala 2.9, which is compatible with
Scala 2.10 but should be the choice of the user to explicitly use the 2.9
version of the scala-extensions library.
Merge pull request #100 from michaeldfallen/removeScala

Removed scala dependencies from the compiler project
Merge remote-tracking branch 'upstream/master'
Add TemplateContext parameter to allow Pragmas to emit valid 'Code' objects including a valid template context.