Completion: higher priority for sorting by deprecated
JS backend: tests for KT-6323 KotlinJS library modules
JS backend: fix KT-6323: KotlinJS library modules

#KT-6323 Fixed
Rename manifest.properties to kotlinManifest.properties to avoid clashing with other resources.
Log error when cannot read properties.
Do not use private Sun API in preloader
Drop "+StdLib" from manifest entries
Avoid redefining kotlin2js task in "ant jslib"

This helps to specify custom runtime for the newly built kotlin2js (which is
supposed to be different for the two bootstrapping steps). Also now it's not
required to launch ant-tools task before jslib to build JS library
Minor, rename JS Ant tasks

To be able to use the build file from the terminal conveniently, make names
shorter and avoid autocompletion conflict with "compiler"
Minor, fix style issues in ant tasks
Use reflection in Ant task to invoke compiler

This will allow a more controlled management of the runtime that the compiler
is linked against.

The test 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 JVM compiler arguments
Use findLoadedClass instead of hand-written cache in ParentLastURLClassLoader
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
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
Refactor CompilerRunnerUtil

Eliminate code duplication, add NotNull, make everything private, etc
Minor style fixes in ParentLastURLClassLoader
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
Minor, rename module to conform to naming style
Include different runtime into plugin for bootstrap build
Rename Maven library kotlin-runtime -> kotlin-builtins

Also replace accidental usages of former kotlin-runtime with kotlin-stdlib