During subtyping/incorporation we transform types (e.g. changing nullability,
 form of the type) and, basically, we're doing this to some FIXPOINT.
 It's important that we use `KotlinType.hashCode()` to compare types, but
 for error types hashCode is a hashCode of its supertype and, for example,
 `makeNullableAsSpecified` method recreate type every time. So, we continue
 to generate new constraints and we'll never stop incorporation algorithm

js.libraries doesn't exist anymore

Fix KT-24542: insert labes for affected loops, breaks and continues
statements during LabeledBlockToDoWhileTransformation

To avoid confusing with platform extension and debugging for 3 hours

When creating multifile facades respect that facade files can be both
    in common and jvm parts

 #KT-23942 Fixed

 #KT-24115 Fixed

Note: can't use Module.cached to calculate data that depends on input
   other than the module itself (isTests in this case)

Do not show bytecode window for non-jvm platform modules

 #KT-24159 Fixed

findClass* are supposed to return a single visible class
    from given scope with given fqname
After sorting FakeFileForLightClass would sometimes be first in the list
    leading to exceptions like KT-24704

  #KT-24704 Fixed

E.g. avoid building release variants for Android
(extremely slow due to proguard minification, optimization)

Currently the test makes more harm than use:
* It is too slow: two executions (with different Gradle versions)
take 5 minute on CI.
* It is unreliable: the test fails on CI for months
with insignificant violation of the memory growth limit.

After this change:
* the memory growth limit is increased;
* the test run count is decreased;
* changes the test to use separate project with minimal amount of classes
(we're not interested in compiler's memory leaks; only Gradle plugin specific ones);

Even if they now have overloads that will be selected when these parameters are omitted.
This is to preserve compatibility with the libraries compiled against the older library.

#KT-24782 Fixed

no sense to keep difference

We run all tests with multiple Gradle versions now,
so parametrized test is not needed anymore.

Test cases are moved to relevant test classes.

testKaptProcessorPath is removed because kapt1 is not supported anymore.

We don't support Gradle <= 3.5 at the moment,
it does not make sense to have the code for Gradle < 2.14