Add highlighting for variables in interpolated strings

We pull the identifiers in `StringInterpolation` from SyntacticInfo, and then
use the SymbolInfo in HighlightingStyle.

The syntax preview can now render deprecated methods with strike-through.
Previously we were building a map of identifier to SyntaxClass and eventually
having it build the style from the SyntaxClass, but in real usage the
HighlightingStyle class does that using Position (and has logic for adding
strikethrough). Now we essentially build a Map of identifier to Position and we
call HighlightingStyle.

This also fixes deprecated method strike-through not being enabled unless
semantic highlighting was enabled for methods (half of ticket #1001584). In
TextPresentationEditorHighlighter we were only calling HighlightingStyle.style
if styling was enabled for that kind of token. Now we call it if the styling was
enabled or if the position says it should be styled, which is true when it is
either marked `deprecated` or `inInterpolatedString`, and HighlightingStyle will
do the right thing whether the style is enabled or not.

SyntaxColouringPreviewText uses a unicode trick to get different coloring for
the variables that are in interpolated strings. Variables that should show up as
in interpolated strings have a different name that looks the same, by using the
"Cyrillic lowercase a" in place of a normal "a". It looks the same, but is a
different character, so the Map[String, ColouringInfo] works. It would be nice
to not specify any of this at all and just compile the code and use normal
highlighting, but it would require having a scala project, compiler, etc all set
up just for previewing.

Fix #1001574, Fix #1001593
Corrections and improvements from code reviews

The name has been changed to "Identifier in interpolated string" since now all
identifiers, including methods, are styled. This is important because writing
s"$method" is valid and should be styled.

We also need to listen for property change events which happen when a user
changes their preferences, so that the editor can be updated.
Removed the extra source folder in sdt.core that allowed master to compile with
both Scala 2.9 and Scala 2.10

Fix #1001674
Correct link in "Run Setup Diagnostics" Dialog

Fixes #1001673
Merge pull request #374 from sschaef/t1001673

Correct link in "Run Setup Diagnostics" Dialog
Merge pull request #356 from dnadolny/interpolated-string-variable-highlighting-1001574

Add highlighting for variables in interpolated strings
Merge pull request #373 from dotta/issue/remove-extra-src-folder-1001674

Removed the extra source folder in sdt.core
JVMUtil went away, workaround that.
Removed the Refined build manager.

Fixes #1001422
Removed exit code mangling, some more output.
Pass default incremental compiler options.
Adapting implicit in predef test following deprecation of implicit test method any2Arrow
Removed remaining @serializable (deprecated in 2.8->2.9)
Use Sbt 0.13.0-M1
Updated Tycho to v0.16.0
Removed scala-2.9.x profile as we no longer need it

* Updated scala version used by scala-2.10.x profile to be Scala
  2.10.2-SNAPSHOT, because that is the targeted Scala version for
  the master branch.
Deactivated 2 tests for PR validation purposes on the 2.11.x branch
Updated Sbt version used by the different Scala profiles

* When building for Scala 2.10.x, let's use Sbt 0.13.0-M1 artifacts
* When building for Scala 2.11.x, let's use the Sbt 0.13.0 SNAPSHOT artifacts

There is an additional catch. When building for Scala 2.10.x, the value of the
property ``sbt.version`` has a trailing ``SNAPSHOT``. Why? Becuase we are using
Scala 2.10.2-SNAPSHOT, and hence the Sbt artifacts have to be rebuilt **every
night**. In the Maven world this means that the artifacts version has to end with
``SNAPSHOT`` (there is really no way around this).

In case you decide to build for Scala 2.10.0 or Scala 2.10.1, then make sure to
pass ``-Dsbt.version=0.13.0-M1`` to the build script (no SNAPSHOT is needed
in this case because the Scala version is stable!).
Updated .classpath of ``sbt.full.library`` project

In commit SHA: 3361828b44521707f32a05b45c2f61e1ffc5f8bc the version of
Scala used to build the codebase changed. Therefore, the Sbt artifacts
exported by default need to be updated accordingly.
Removed JVMUtils uneeded spare parts