Debugger changes for expression evaluator

ScalaDebugger now capture frame indexes. Frame indexes are needed
to evaluate expressions on stack frames differrent than current one.

Correct SuspendPolicy handling. Before, debugger always suspended thread,
now suspending whole VM is correclty handled.

DebugTarget now stores classpath of underlying project, which is used to
load files to inspect for generics, imports etc.

Minor corrections to ScalaClassFile.
Implementation of expression evaluator and conditional breakpoints based
on JDI.

Allows user to evaluate any Scala expression in context of some breakpoint
during debug. Expression is transformed in multiple phases and evaluated
using calls to remote, debuged machine and result is fetched back to user.

Because of complexity of Scala language, implementation details of JVM
platform and necessity for manual evaluation not all Scala features are
supported yet.

Co-authored-by:
 - Pawel Batko <pawel.batko@gmail.com>
 - Piotr Kukielka <piotr.kukielka@gmail.com>
 - Jerzy Muller <sidus.gemini@gmail.com>
 - Michal Pociecha <michal.pociecha@gmail.com>
 - Krzysztof Romanowski <romanowski.kr@gmail.com>
User interface for expression evaluator

Complete with history command, tree view for values, simple content
proposal and multiple configuration parameters.
RunSelectionInInterpreter action added

Runs currently selected text in expression evaluator view.
AUTHORS file updated with names of expression evaluator authors