Basic deploy of AngularJs + RequireJs + Bootstrap

AngularJs, RequireJs and Bootstrap have been deployed into the webapp, by
including the dependencies via WebJars. Also, an AssetsController scala file
has been created to unify different package names in controllers (Play's
default "controllers" and mine "es.uvigo.esei.tfg.smartdrugsearch.controller"),
that were causing some weird and ugly inconsistencies both in the Routes config
file and in views.

Also, to also improve consistency, and since Play's generated Scala code from
views use a package name relative to its path (so, if the path was
"src/main/view", it will put it in package "view"), a directory tree of all
packages has been created, and all code moved into it. Note that this tree
structure is not required nor enforced by Scala or Play, as opposed to Java,
and things have been working well without it; it's just done for consistency
with the generated Play's Views code.
Implement search and document view in webapp

Web interface for search and document details has been implemented by using
angular.js and bootstrap. A couple of controllers, templates and stylesheets,
nothing interesting there.

JavaScriptRouterController has been removed, because it causes a lot more
headaches than it solves, and code is a lot cleaner and easier to manage when
not fully coupling client code (JavaScript) and server code (Scala). With that
previous "jsRoutes" approach, instead of simply sending HTTP requests and
receiving responses to the API routes of server, we would use intermediate
objects mapping those routes, but they will expose (and require to use) some
implementation details of the Scala code (mainly: package and name of
controllers), which is totally insane: I want my client code to me as much as
decoupled from my server code as It can.

Some bugs in Searcher and some improvements (added cached responses for
documents) have been also made.