SI-4365 nondeterministic failure in asSeenFrom

Under some order-dependent conditions (if source files arrive
in one order it happens, in the other order it does not) more
than one set of type parameters are created for a given class.
Previously this would lead to a crash in asSeenFrom when a type
parameter had to be matched up with a type application.

Now when that situation arises I compare them by name and log
a dev warning if it hits. This does not risk anything undesirable
happening because the wayward type parameter's owner is always
the right class; it's only the class type parameters which don't
include the wayward one. Since in a given type parameter list
names are unique, we have enough information to salvage the
search.
check added instruction to ASM MethodNode
Created utility function for dropping by-name-ness.

And applied it in three locations.
SI-7403 Stream extends Serializable

Additionally, add @deprecatedInheritance to warn creators of
custom subclasses that the class will be sealed in the future.
SI-7421 remove unneeded extra-attachement in maven deploy
static methods may have local variables too, some day
removing remnants from the GenJVM era
another GenJVM remnant that goes away
Merge pull request #2451 from magarciaEPFL/backendish4

check added instruction to ASM MethodNode
role played by magic constant in ScalaSigBytes
Merge pull request #2430 from paulp/issue/4365

SI-4365 nondeterministic failure in asSeenFrom
Merge pull request #2442 from soc/SI-7403

SI-7403 Stream extends Serializable
Merge pull request #2450 from huitseeker/issue/SI-7421

SI-7421 remove unneeded extra-attachement in maven deploy
Merge pull request #2452 from magarciaEPFL/backendish5

cleanup of old stuff from the GenJVM era
Merge pull request #2447 from paulp/pr/byname

Created utility function for dropping by-name-ness.