Updated to IDEA 135.667 (13.1.2 EAP)
KT-4794: Added functionality to KT-4574: Split If. Intention is now offered inside IF keyword
Merge pull request #431 from gavinkeusch/split_if_new

KT-4794: Added functionality to KT-4574: Split If. Intention is now offered inside IF keyword
Simplify codegen for trait methods with implementations

- use existing framework (FunctionCodegen.generateMethod) which will take care
  of all subtleties of method generation (bridges, annotations, thrown
  exceptions, etc)
- call to "generateThisOrOuter" was not needed, since when we're generating
  delegation to TImpl, "this" is always "ALOAD 0"
Minor, move and rename getExceptions

Should only be used in FunctionCodegen from now on, because every method
generation should go through FunctionCodegen
Refactor bridges algorithm in codegen

- fix a typo (which apparently didn't matter)
- queue now always contains originals, no need to invoke getOriginal()
- no need to add current descriptor's original anymore, this was a hack working
  around a problem with trait-impl which was fixed by another change
- a small optimization: don't do anything for constructors
Generate bridges for fake overrides when needed

 #KT-3985 Fixed
 #KT-4145 Fixed
Consider all real functions, not only declarations in bridge codegen

There should be bridges to all of the functions present in bytecode
Minor, add bytecode text test on bridges for fake overrides
Minor, catch all exceptions in asm verification in tests

E.g. ClassFormatError
Refactor ImplementationBodyCodegen.getTraitImplementations()

Make it static, extract a method which finds an implementation in a trait for a
fake override
Rewrite bridge generation to Kotlin, make it abstract
Don't generate bridges in light classes mode
Generate bridges for trait implementations properly

The intent was to keep the bridge codegen model as simple as possible: we
should be able to figure out all necessary bridges only by a minimal interface
that FunctionHandle provides (isAbstract, isDeclaration, getOverridden)

Add different tests for bridges

 #KT-318 Obsolete
Fix incorrect diagnostic message for CONFLICTING_OVERLOADS

- the member and the container were mixed up
- don't output "defined in" part of the message, because we tell later where
  it's already defined in
- fix an instability of the diagnostic order in OverloadResolver by using
  LinkedHashSet
Escape HTML in IDE diagnostic messages

Print "<root>" instead of an empty string for CONFLICTING_OVERLOADS diagnostic
Don't print descriptors' toString() in diagnostic messages

Use DescriptorRenderer.TEXT instead, it doesn't print the debug information