SI-5361 Avoid cyclic type with malformed refinement

The statement `val x = this` in the refinment type:

    (new {}): {val x = this}

is lazily typechecked, in order to, according to the comment
in `typedRefinment, "avoid cyclic reference errors".

But the approximate type used ends up with:

    Refinment@1(
      parents = [...]
      decls = { val x: Refinement@1 })

This commit eagerly checks that there is no term definitions
in type refinments, rather than delaying this.

This changes the error message for SI-3614.
SI-5390 Detect forward reference of case class apply

Refchecks performs (among others) two tasks at once:

  - detecting forward references
  - translating `qual.Case(...)` to `new qual.Case(...)`

As is often the case with such multi-tasking tree traversals,
completion of one task precluded the other.
SI-3995 Exclude companions with an existential prefix.

In `(qual: Q).apply(expr)` where `expr` must be implictily
converted to a path dependent type `T` defined in `qual`,
we were looking for companion implicits via a path prefixed
by an existential skolem `_1`. These aren't much good to us,
as when we try to feed them into `mkAttributedQualifer`, a
crash rightly ensues.

This commit excludes companions prefixed by an existentially
bound path.
SI-5361 Refactor in accordance with review comments.

Check for malformed stats in the refinement body in
the same place we check for erroneous parents.
Expand test with a stably qualified example.

In the example below, we need a view from
`String => l.F0`, and the companion object `FO` is
reachable by a stable, non existentially-bound path.

    class Lift {
      def apply(f: F0) {}

      class F0
      object F0 {
        implicit def f2f0(fn: String): F0 = ???
      }
    }

    object Test {
      val l = new Lift
      l.apply("") // okay
    }

Followup for SI-3995
SI-6548 reflection now correctly enters jinners

When completing Java classes, runtime reflection enumerates their
fields, methods, constructors and inner classes, loads them and
enters them into either the instance part (ClassSymbol) or the
static part (ModuleSymbol).

However unlike fields, methods and constructors, inner classes don't
need to be entered explicitly - they are entered implicitly when
being loaded.

This patch fixes the double-enter problem, make sure that enter-on-load
uses the correct owner, and also hardens jclassAsScala against double
enters that can occur in a different scenario.

Since the fix is about Java-compiled classes, the test needs *.class
artifacts produced by javac. Therefore I updated javac-artifacts.jar to
include the new artifacts along with their source code.
cosmetic renamings in runtime reflection

initClassModule => initClassAndModule
createClassModule => initAndEnterClassAndModule
SI-6555 Better parameter name retention

We were losing track of parameter names in two places:

  1. Uncurry was using fresh names for the apply method
     parameters during Function expansion. (The parameter names
     in the tree were actually correct, they just had synthetic
     symbols with "x$1" etc.)
  2. When adding specialized overrides, the parameter names
     of the overriden method were used, rather than the parameter
     names from the overriding method in the class to which we are
     adding methods.

The upshot of this is that when you're stopped in the debugger in
the body of, say, `(i: Int) => i * i`, you see `v1` rather than `i`.

This commit changes Uncurry and SpecializeTypes to remedy this.
DRYer crash reports.

 - Add the supplementary message only once per run, so we don't
   output the same information as we bubble up through a sequence
   of well-intentioned exception handlers.
 - In Driver, don't report message of a `FatalException`
   immediately after reporting the message and stack trace.
    - Rename `logThrowable` to `reportThrowable`, which is what it
      actually does.

The difference in output is visible:

  https://gist.github.com/4242138
s/SuperCallArgs/SuperArgs/

Applies a minor renaming that I failed to thoroughly perform
in the last pull request which refactored parent types.
prevents spurious kind bound errors

The patch adds a check which makes sure that the trees we're about to
report aren't already erroneous.
SI-6795 Adds negative check for "abstract override" on types in traits

"abstract override" shouldn't was being allowed on types in traits but the result
made no sense and the spec says that shouldn't be allowed.
SI-6795 Simplify errors related to "abstract override" on type members

Instead of saying "only allowed on non-type members of traits" use
separate errors for "not allowed on types" and "only allowed on members
of traits"
Fixes SI-6758: force LazyAnnnotationInfo for DefDef and TypeDef

Looks like the change in 25ecde037f22ff no longer forced
lazy annotations for some of the cases.
Also removed forcing for PackageDef annotations as we currently
don't support them.
SI-6288 Position argument of unapply

`atPos(pos) { ... }` doesn't descend into children of
already positioned trees, we need to manually set the
position of `CODE.REF(binder)` to that of the stunt double
`Ident(nme.SELECTOR_DUMMY)`.
Merge pull request #1737 from retronym/ticket/6555

SI-6555 Better parameter name retention
Merge pull request #1738 from retronym/topic/dryer-crashes

DRYer crash reports.
SI-6288 Fix positioning of label jumps

ICode generation was assigning the position of
the last label jump to all jumps to that particular
label def.

This problem is particularly annoying under the new
pattern matcher: a breakpoint in the body of the final
case will be triggered on the way out of the body of
any other case.

Thanks to @dragos for the expert guidance as we
wended our way through GenICode to the troublesome
code. Chalk up another bug for mutability.

I believe that the ICode output should be stable
enough to use a a .check file, if it proves otherwise
we should make it so.
SI-6288 Remedy ill-positioned extractor binding.

The call to `Option#get` on the result of the
unapply method was unpositioned and ended up
with the position of the `match`.
Expand pattern match position tests.

 - Adds tests for unapplySeq and unapply: Boolean.
   Both seem to be well positioned after the previous
   changes.