SIP-14 improvements

Add missing canonical combinators:
  `def transform[S](f: Try[T] => Try[S])(implicit executor: ExecutionContext): Future[S]`
  `def transformWith[S](f: Try[T] => Future[S])(implicit executor: ExecutionContext): Future[S]`
  `def flatten[S](implicit ev: T <:< Future[S]): Future[S]`

Add missing utilities:
  `val unit: Future[Unit]` in `object Future`
  `val never: Future[Nothing]` in `object Future`

Refactors:
  the scala.concurrent.Future trait to not explicit create any Promises,
  so that implementations can control implementation type,
  this is mainly facilitated through adding of the `transform` and `transformWith` methods.
  the implementation of ExecutionContextImpl has been cleaned up

Securing:
  Add a self-check in completeWith and tryCompleteWith to avoid cycles in trait Promise
  Capping the maximum number of Threads for the global ExecutionContext to the max parallelism
  Implementing (almost) all `Future` combinators on `transformWith` and `transform` means
  that DefaultPromise linking works on both (flat)map and recover(With)

Removes:
  the private internalExecutor method in favor of an import in trait Future
  the private internalExecutor method in favor of an import in trait Promise
  the AtomicReferenceFieldUpdater in AbstractPromise since we're using Unsafe
  scala.concurrent.impl.Future is no longer needed

Deprecates:
  Future.onSuccess - discourage the use of callbacks
                     (and is also redundant considering `foreach` and `onComplete`)
  Future.onFailure - discourage the use of callbacks
                     (and is also redundant considering `onComplete` and `failed.foreach`)
  ExecutionContext.prepare - it was ill specced and it is too easy to forget to call it
                     (or even know when to call it or call it more times than needed)

Reimplements:
  failed - in terms of `transform`
  map - in terms of `transform`
  flatMap - in terms of `transformWith`
  recover - in terms of `transform`
  recoverWith - in terms of `transformWith`
  zip - in terms of `flatMap` + `map`
  fallbackTo - in terms of `recoverWith` + `recoverWith`
  andThen - in terms of `transform`

  Documentation:
    Almost all methods on Future and Promise have been revisited and had their ScalaDoc updated

  Tests:
      Yes
Hi Viktor,

reading the conversation was very interesting. 

It reflects my personal thoughts. I found the `prepare` on `ExecutionContext` difficult to understand and to master.
When I work with `ExecutionContext` directly, I prefer to catch the caller's context in the constructor directly.
It was my first method to catch the SLF4J MDC (see [Second solution with a custom execution context](http://yanns.github.io/blog/2014/05/04/slf4j-mapped-diagnostic-context-mdc-with-play-framework/) - sorry, no anchor link)

Therefore I can understand this method can be deprecated.

On the other hand, if we deprecate `ExecutionContext.prepare`, we deprecate the Akka `Dispatcher.prepare` as well.
With an akka Dispatcher, there is not the possibility to catch to caller's context with the EC constructor. The dispatcher is created once. After that, the dispatcher can instantiate Execution Contexts. Using the `prepare` method is the only way I see to instantiate an EC. Or do you see other possibilities?

In my opinion:
- either `Dispatcher.prepare` should remain not deprecated
- or `Dispatcher` should provide a new API to instantiate a new EC.

What do you think about that?