Updated all benchmarks to Play 2.3.6 and Scala 2.11.4.

Updated Ebean benchmarks to include missing tests as well as include HikariCP version.
Moved `/plaintext` tests from JPA/Ebean benchmarks to the `play2-java` benchmark as per https://github.com/TechEmpower/FrameworkBenchmarks/pull/1149#dis
Added BoneCP qualifier as per https://github.com/TechEmpower/FrameworkBenchmarks/pull/1149#discussion_r19584629 and changed names accordingly.
You're right that the update logic should be running in the `dbEc`. My only concern is that `getRandomWorlds` will run in the `dbEc`, flatMap will run in the default EC and then `updateWorlds` will run in the `dbEc` again. We want to avoid bouncing between different thread pools as much as possible because it will have a noticeable effect on performance.

To avoid thread pool switching I suggest is that you change the `flatMap` to a `map` and change the `map` to run the update logic in the `dbEc`. You can do this by moving the update logic out from `updateWorlds` and into the `map`'s `Function1` and then supplying `dbEc` as the `map`'s last argument.

By the way, there are other similar optimisations that we could theoretically do in this benchmark code, but I'm trying to avoid anything too complicated. I'm only suggesting this optimisation because I don't think it will compromise the readability of the code.