Don't log stack trace for warning

These stack traces are confusing and create a feeling that an exception was
thrown
Extract DescriptorUtils.getContainingModule()
Pass module to GenerationState

- get rid of a hack there which was used to obtain any module, to be used in
  ReflectionTypes
- delete unused getError() in LightClassConstructionContext which was always
  null
- fix some minor warnings
Use module instead of KotlinBuiltIns in ReflectionTypes
Introduce module 'reflection', move KFunctionN to it

Metadata for KFunction classes is now longer serialized along with built-in
classes. This effectively means that it's no longer possible to find KFunction
classes via dependency on built-ins. There should be a kotlin-runtime library
in the specified classpath for reflection types to be resolvable.

A lot of tests were moved and changed, because tests on callable references
require stdlib in classpath from now on
Split ant 'runtime' target to 'runtime.jvm' and 'stdlib'
Move KFunctionN classes to package "kotlin.reflect"
Add default import "kotlin.reflect"
Create error type if reflection class isn't found

Introduce a new diagnostic fired when reflection types aren't found in the
classpath
Introduce FunctionImpl and ExtensionFunctionImpl classes

Old FunctionImpl0,1,2,... will be dropped since they had no purpose
Drop FunctionImplN and ExtensionFunctionImplN

We have FunctionImpl and ExtensionFunctionImpl classes now (2 classes, not 46)
Fix generic signature for SAM adapters and constructors

SAM-related code in codegen was using JavaClassDescriptor directly, which has
an erased signature. Create and use a new abstraction SamType which has a full
generic signature of a type which was used in the SAM construct
Move and rename KFunctionImpl classes

Move from package "kotlin.reflect" to "kotlin.reflect.jvm.internal". They are
internal detail of the compiler and should not be used directly (especially now
that "kotlin.reflect" is in default import paths).

Also rename "KFunctionImplN" to "KFunctionNImpl", because this name makes more
sense
Change logic of loading "suppress" annotation class descriptor

Instead of loading the descriptor and checking equals(), we now check if the
annotation is in fact "suppress" by simply comparing its FQ name. This allows
us to suppress warnings while compiling built-ins: the problem is that
built-ins have its own "suppress" annotation class (defined in the sources)
which differs from the one loaded by the compiler (from kotlin-compiler.jar)
Minor optimization in KotlinBuiltIns.isSpecialClassWithNoSupertypes
Increase ABI version after changes to FunctionImpl* classes