Introduce Variable: Amend semicolons to updated expression
 #KT-2098 Fixed
Change Signature: Do not fail on dynamic calls. Show error messages instead
 #KT-6529 Fixed
Rename: Show error message when trying to rename dynamically invoked function/property
Introduce Variable: Do not create separate template to edit type reference
 #KT-4314 Fixed
Resolve dangling annotations in files and class bodies
J2K: fixed duplicated open modifier generated
Use reflection in Ant task to invoke compiler

This will allow a more controlled management of the runtime that the compiler
is linked against. Incidentally this also allows Ant task to use any of
compiler arguments via <compilerarg> because Ant task is now just a facade for
the CLI compiler.

The test "wrongArguments" is deleted because the full compiler usage is now
printed out on a wrong <compilerarg>, and this will become inconvenient to
update with each change in compiler arguments

 #KT-5618 Fixed
fixup! Use reflection in Ant task to invoke compiler
fixup! Use reflection in Ant task to invoke compiler
fixup! Use reflection in Ant task to invoke compiler
Compile kotlin-runtime-minimal.jar, run proguard against it

ProGuard complains if we're trying to shrink compiler with the full runtime in
dependencies because for the compiler produced on the first step of bootstrap
these two jars contain conflicting classes. This won't matter in the final
distribution because we will strip 'core' modules from compiler.jar. But this
matters in the first step because core will be different in the compiler (used
to load compiled class files) and in the reflection (used to introspect symbols
at runtime).

kotlin-runtime-minimal.jar still contains the complete reflection API and some
stub implementations in module 'reflection.stub.jvm', but doesn't have core, so
it won't cause a proguard error
fixup! Compile kotlin-runtime-minimal.jar
fixup! Compile kotlin-runtime-minimal.jar
Rework bootstrapping compiler with runtime in build.xml

Do not pack the runtime into the compiler on the first step of bootstrap, but
rather leave it as a separate file named kotlin-runtime-internal-bootstrap.jar.

This new solution will allow compiler to use its own classes from "core", not
the ones used by the runtime it depends on
fixup! Rework bootstrapping compiler with runtime in build.xml
Rename MessageRenderer constants
Refactor CompilerRunnerUtil

Eliminate code duplication, add NotNull, make everything private, etc
fixup! Refactor CompilerRunnerUtil
fixup! Refactor CompilerRunnerUtil
Load compiler dependencies in a separate class loader in IDE compiler runner

To be able to invoke the intermediate compiler built on the first step of
bootstrap: in contrast to the distributed compiler, it's incompatible with the
runtime produced by itself and should instead be run with the runtime in the
classpath which was used to compile it.

Drop the non-preloader mode of running compiler, because it would require using
a special parent-last class loader with exceptions specified by ClassCondition

1