Adds routes hyperlinking support for Scala controllers

The hyperlink computer uses the presentation compiler to find a matching method.
Depending if the controller is Scala or Java, creates the right IHyperlink object.

Fix #3
Bases RouteAction on ControllerMethod
Merge pull request #94 from skyluc/issue/scala-hyperlink-in-routes-3

Adds routes hyperlinking support for Scala controllers
Some small code clean-up

* Added `override` keyword in the relevant places.
* Added return type information to public methods.
* `RoutePartitionTokeniser` is now a class.
* Changed `HTTPKeywords.words` to `HTTPKeywords.Methods`.
* Removed some unused code in `RouteDocumentPartitioner`
Added mockito to the test project

This is needed by the next commit to compile.
Added additional profile to ./build.sh script

The additional scala-2.10.x profile is needed becuase of the POM refactoring
done in SHA: 79b29821d72b94b666462f9bbfe545d951b5a835
Created WordFinder class and unit tests

In order to create the unit tests an additional `editor.tests`
bundle was created.
Completion for HTTP methods in route files

Fixes #81
Fixed some issue with the partitioning of Route files

* Wrote a number of tests for ROUTE_HTTP partitioning and
fixed a number of bugs related to incorrect partitioning.

* Moved down some logic from ``PlayDocumentPartitioner`` to
``TemplateDocumentPartitioner``. The ``PlayDocumentPartitioner`` is used by
both the template and the route editor to partition the file. The former
implementation of ``PlayDocumentPartitioner.getPartition`` was preventing HTTP
method completions to properly work in some corner case. Hence, I moved the
blamed portion of the code in the ``TemplateDocumentPartitioner`` subclass.
Though, I'm actually not convinced that code is needed in the first place.

Note about the change in ``PlayDocumentPartitioner``

The change in ``PlayDocumentPartitioner`` is a side-effect of the changes I've
made in the ``RoutePartitionTokeniser``. My gut feeling is that the current way
we compute the dirty region should be improved, but I'd rather do this in a
separate PR.

Also, this seemingly innocuous change could lead to new issues in the Template editor,
because the PlayDocumentPartitioner is used by both the Route and the Template editors.
I've done some minimal monkey testing in the template editor after this change, and I haven't
seen any issue, but I can't state I'm confident nothing bad will happen out of this.

Fixes #100
Merge pull request #101 from dotta/issue/completion-for-HTTP-methods-81

Issue/completion for http methods 81
``RoutePartitionerTokeniserTest`` can now be run headless-ly

* Renamed ``Util`` to ``EditorUI`` because ``defaultLineSeparator`` requires
  loading some UI class, and that is a problem because our CI server can only
  build headless-ly.

* Created ``Editor`` and ``Util.getEditorDocument`` on it.

* ``RoutePartitionTokeniser`` uses now the Eclipse `Document`
instead of raw text. The huge advantage is that there is no longer a need
for handling the line separator, as the `Document` class already contains
the logic for doing this properly.

The test failure was introduced in SHA: 6b796dbde3547b0bf445aa19a30b37998c74d16d
Merge pull request #102 from dotta/transient/fix-jenkins-build

``RoutePartitionerTokeniserTest`` can now be run headless-ly
Quick-assist "Add route entry" for for Java sources.

Fixed #86.