needed to implement @PreDestroy

The problem was in the "more specific" relation, that didn't pay enough attention to varargs.
The correct behavior is in the spirit of JLS 15.12.2 (as of Java 5):
 * a fixed-arity function always wins over a variable-arity functions
 * if two vararg functions are compared, their parameters are checked for subtyping.
  In the latter case, the candidates may have different number of formal parameters, so we
  compare the matching parts and then check the rest against the vararg parameter.

 #KT-1835 Fixed

The problem was in the "more specific" relation, that didn't pay enough attention to varargs.
The correct behavior is in the spirit of JLS 15.12.2 (as of Java 5):
 * a fixed-arity function always wins over a variable-arity functions
 * if two vararg functions are compared, their parameters are checked for subtyping.
  In the latter case, the candidates may have different number of formal parameters, so we
  compare the matching parts and then check the rest against the vararg parameter.

 #KT-1835 Fixed

When a non-vararg parameter gets spread with a '*' in front of it, a "weak error" is returned.
A candidate with a weak error in parameter matching is type-checked, but not successful.

- interfaces MemberPrioritizer, ResolutionCandidate introduced
- CallTransformationStrategy will be responsible for variable with 'invoke' method as function resolve

#KT-1831 Fixed

 #KT-1630 fixed

 #KT-1822 fixed

 #KT-1680 fixed

 #KT-1778 fixed

 #KT-1806 fixed

 #KT-151 Fixed

Visibilities.INHERITED constant added (occurs only during resolve), changed after overridden descriptors resolve
Fake descriptors are created for invisible properties as well (is necessary for better error reporting)

changed resolution order: first priority is 'local extensions; members; nonlocal extensions', than by implicit receivers (before was vice versa)

 #KT-1781 Fixed

 Now, if foo() and foo(vararg bar) both match the call site, the first one is preferred

We used to have a triple (errorStream, messageRenderer, verbose) to represent the error reporting strategy.
 Now we have a single MessageCollector abstraction for this.
 As the MessageCollector abstraction was extracted, the need to CompilerMessageLocation and CompilerMessageSeverity arose, too.

 #KT-1645 fixed

* custom versions
* normalization code moved out of norializer
* hide DESCRIPTOR_TO_DECLARATION (make package local)

* assert runtime implementations from JetStandard* are not loaded
  by JavaDescriptorResolver
* fix wrong @JetMethod in jet.Iterator
* fix jet.Iterator ns was created
* fix incorrect number of functions and tuples in JetStandardClasses
* added TODO about inconsisten Tuple class

 #KT-1763 fixed

as requested by http://confluence.jetbrains.net/display/JET/Code+Conventions+for+Java

(sed is your friend)

* add assertion
* fix tests
* #KT-1748 Fixed

KT-1237 Auto-completion of "return" keyword should not insert space after it when in a method returning Unit

 #KT-1237 fixed
 #KT-1238 fixed

 #KT-1137 fixed

 #KT-1666 fixed

Implemented better rendering for parameters with default values in decompiler and descriptor renderer.

 #KT-1582 fixed