Refactoring in `ScalaClasspathContainers`

Pushed up `libraryEntries` method so that it can be used by the two subclasses
of `ScalaClasspathContainerInitializer`
Add an option to show API diffs when building

The incremental compiler can print diffs that explain
why additional files need recompilation. This commit adds
the diffutil.jar and a user-level option.

Fixed #1001952
Removed special support for Scala continuations

The Scala IDE used to package the continuations plug-in to match the Scala
distribution.  While this conveniency was appreciated by the few using
continuations in their projects, it imposed a technical debt on the Scala IDE
codebase (have a look at how the compiler `Settings` used to be instantiated).

Recently, the continuations plug-in has been refactored and splitted into two
separate JARs (a compiler plug-in, and a library). After this modularization,
the Scala IDE codebase could no longer be compiled inside Eclipse because the
continuations library isn't included in the project's classpath. Of course, we
could implement a workaround to restore the functionality, but it just doesn't
seem worth the time, considering the Scala Team has deprecated the
continuations plug-in and will effectively drop supporting it the moment 2.12
is released.  Hence, the decision of dropping the out-of-the-box support in the
Scala IDE.

From now on, if you want to use continutions in a project, you will have to
provide the location of the continuations JAR via the -Xplugins setting.

Finally, a couple of tests exercicing the behavior of both the presentation
compiler and the build compiler when compiling a sourcefile that requires the
continuations plug-in are now executed only for Scala 2.11 or later. This is
needed because the continuations.jar is no longer loaded when starting the
compiler inside Eclipse, and that turns out to affect semantic of programs
using continuations in Scala 2.10, because the compiler does no longer report
an error if a source file (requiring continuations) is compiled without passing
the flag to enable the plugin. Why? Because up until Scala 2.10 the compilation
error is reported by the continuations.jar (!!). Of course, that error cannot
be reported if the continuations.jar isn't available anymore (which is the
whole point of this commit).  The behavior with Scala 2.11 is different because
the continuations library has been moved out of the scala library (see
https://github.com/scala/scala/commit/858a5d513779f4af6f12c0a530bdeceb7a7fd4d9),
and hence a compilation error is reported whenever a source is compiled without
the continuations library in the classpath. That explains why the tests are now
only executed on 2.11+.

This commit undos all changes related to supporting continuations made by
@adriaanm in https://github.com/scala-ide/scala-ide/pull/604

Fix #1002012
Fix #1002011
Merge pull request #617 from dotta/issue/remove-continuations-plugin-support

Issue/remove continuations plugin support
Merge pull request #615 from dragos/api-diff

Add an option to show API diffs when building
Fixed NPE on quick assist proposals

In the former implementation, the implicit conversion `Predef.refArrayOps`
could be applied on a `null` value, because `null` was returned if
`corrections.isEmpty` was true, leading to a NPE.

Fix #1002014
Merge pull request #618 from dotta/issue/npe-on-quickassist-1002014

Fixed NPE on quick assist proposals
Using the enclosed type to fix completion and imports for inner classes.

Make sure that the enclosing object is passed to the indexer also for modules.

Fix #1002002
Merge pull request #607 from tbje/fix-inner-type-completion-#1002002

Using the enclosed type to fix completion and imports for inner classes.