Restrict Import-Package for scala.*

Restrict the Import-Package OSGi manifest entry to match only binary compatible scala.* packages. This is necessary, because the Scala OSGi versions do not match the OSGi semantic versioning policy and are not binary compatible between their OSGi minor versions. This means that e.g. the scala-compiler-2.11 bundle will never work if it imports a scala.* package from 2.10 or 2.12. Thus this patch enforces a tight version range, only accepting versions within the same minor version. E.g. Applied to version 2.11.1 the range would expand to "[2.11,2.12)".

Additionally, a Java 6 execution environment will be enforced for OSGi.

All module bundles need to have their own version numbers. This was not the case before this commit. Although these module bundles were only build for testing, they are needed to be correct, now, that we have stricter package import constraints and some test cases rely on them.
Add JavaSE-1.7 to set of required execution environments.

Without it, Equinox on Java 7 might spit out some warnings, which might lead to the wrong impression, that the Scala bundles are not well supported for newer platforms.
Refined package imports for scala modules.

Made scala.xml.* import optional and removed scala.util.parsing.json import.
Re-added the scala.util.parsing package import, with optional resolution.
SI-8475 Fix off by one in GroupedIterator when Streaming

This also affected sliding and grouped since they defer to GroupedIterator
SI-8578 Avoid fresh name clashes under -Ydelambdafy:method

It is important to append the fresh 'N' after '$'. Otherwise, we
find out the hard way that ("foo$11" + "1") == ("foo$1" + "11").
SI-8578 Avoid another potential fresh name clash

No test case for this one, but see the preceding commit for
the class of bug that I'm trying to avoid.
SI-8553 WrappedArray throws exception on lastIndexWhere when index out of range

Adds a check in `IndexedSeqOptimized#lastIndexWhere(A => Boolean, Int)`
to begin searching in the end of the collection if `end` is greater than
the collection's length.

Discussed in
https://groups.google.com/d/topic/scala-internals/-MacXivbY0Q/discussion.
Merge pull request #3742 from retronym/topic/8578

SI-8578 Avoid fresh name clashes under -Ydelambdafy:method
SI-8582 Pending test for InnerClasses bug in GenBCode

As seen in a runtime reflection failure in Slick during a GenBCode
enabled run of our beloved Community Build.
Merge pull request #3744 from retronym/ticket/8582

SI-8582 Pending test for InnerClasses bug in GenBCode
SI-8507 Avoid lazy val in StringContext

This mild refactor eliminates the lazy val StringBuilder
and arguably makes the code easier to read.

There is a small unit test but no benchmark to prove
anything useful about performance. The ticket notes
contention due to lazy implementation.
Allow tracing methods and classes in GenBCode
Fix BeanInfo generation for GenBCode
SI-8582 emit InnerClasses attribute in GenBCode

I removed the `-bcode` test since we have a build that passes
`-Ybackend:GenBCode` to all tests.

Short intro do the [`InnerClass` attribute][1]:

  - A class needs one `InnerClass` attribute for each of its nested
    classes

  - A class needs the `InnerClass` attribute for all (nested) classes
    that are mentioned in its constant pool

The attribute for a nested class `A$B$C` consists of the long name of
the outer class `A$B`, the short name of the inner class `C`, and
an access flag set describig the visibility.

The attribute seems to be used for reflection.

[1]: http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.7.6
Move t8582 to test/files/jvm
Merge pull request #3745 from lrytz/t8582

SI-8582 emit InnerClasses attribute in GenBCode
SI-8587 Explicitly document forall/exists for empty collections

This behaviour isn't always intuitive for newcomers.

Also changes inadvertant doc comment to an impl. comment.
SI-8591 Scaladoc: Problem with scrolling under Safari on iOS
SI-8574 Copy @SerialVersionUID, etc, to specialized subclasses

The test case demonstrates that this is important for serialization
and for strictfp. (Although the latter is still pretty broken,
see SI-7954.)

Now that the synthetic subclass of `Tuple2[Int, Int]` also has the
`@deprecatedInheritance` annotation, I had to change the spot that
issues this warning to be silent after the typer phase. Otherwise,
we get two warnings in `run/t3888.scala`. This also remedies double
warnings that were incurred in `neg/t6162-inheritance`.