New take on SI-6534, value classes.

Don't prohibit equals and hashCode in universal traits;
instead, always override them in value classes.
Fixes SI-5031 for separate compilation scenario.

When you have a conflicting member in package object and normal package that share the same namespace we remove the latter ClassSymbol from the scope. Now, this has an unpleasant consequence that companionClass/companionModule/companionSymbol no longer work correctly as they rely on finding the correspondent symbol using decls of the owner.
This fixes the problem of SI-5031 for separate compilation. Why the above change matters for finding foo.bar.Foo? Because when parsing the class we needed information about the static module (and we have the correct module symbol when completing the info). It's just that 043ce6d0565c9d5d960 relied on no longer valid assumptions. So we were getting NoSymbol and sym.exist was failing.

Obviously a more complete solution would be better if we didn't rely on the scope but that's too big to change for 2.10.0.
SI-6581 fixed by inlining `Actor.self`.

This avoids the necessary type cast that was preventing leakage of internal migration classes.

Review by @phaller
Modification to SI-6534 patch.

Only exclude hashCode and equals from being overridden in
value classes, not other synthetics which may turn up such
as case class methods.
Fixes SI-6500 by making erasure more regular.

With the introduction of value classes, erasure uses specialErasure where a value class C with underlying type T is unboxed to an ErasedValueType. ErasedValue types are eliminated on phase later, in post-erasure. This was done everywhere, except in the parameter types of bridge methods. That was a mistale, because that way  bridge methods could not do the boxing/unboxing logic triggered by ErasedValueTypes.

Note: there is one remaining use of erasure (not specialErasure) in Erasure.scala. I put in a comment why that is OK.
Removing actors-migration from main repository so it can live on elsewhere.

* Removes actors-migration hooks from partest
* Removes actors-migration code
* removes actors-migration tests
* removes actors-migration distribution packaging.
SI-6556 no assert for surprising ctor result type

Previous fix to value classes uncovered some questionable cases in the backend where result types of constructor signatures are surprising. It's not a big deal because these types will be ignored afterwards anyway. But
the method uncovered some questionable situations which we should follow up on. However, breaking 2.9 code because of this is way too harsh. That's why the asserts were converted to warnings.

review by @paulp, @adriaanm
SI-6578 Harden against synthetics being added more than once.

Don't add synthetic methods if they already contain synthetic
methods from the set we're about to add.
Merge pull request #1532 from hubertp/2.10.0-wip-issue/5031

Fixes SI-5031 for separate compilation scenario.
Merge pull request #1536 from vjovanov/issues/SI-6581

SI-6581 fixed by inlining `Actor.self`.
Merge pull request #1543 from adriaanm/paulp-add-synthetics-once

SI-6578 Harden against synthetics being added more than once.
Merge branch '2.10.0-wip' of github.com:scala/scala into 2.10.0-wip
Removing actors-migration from main repository so it can live on elsewhere.

* Removes actors-migration hooks from partest
* Removes actors-migration code
* removes actors-migration tests
* removes actors-migration distribution packaging.
Merge pull request #1541 from jsuereth/fix/SI-6577-actors-migration

SI-6577 Make actors-migration an external module
Merge pull request #1542 from adriaanm/odersky-ticket/6556v2

SI-6556 no assert for surprising ctor result type
Merge pull request #1540 from odersky/ticket/6500

Fixes SI-6500 by making erasure more regular.
Merge pull request #1526 from paulp/value-classes/6534-equals

New take on SI-6534, value classes.
SI-6399 Adds API docs for Any and AnyVal

- Updates AnyVal docs to address value classes.
- Updates Any docs to address universal traits.
Remove implementation details from Position (they are still under reflection.internal). It probably needs more cleanup of the api wrt to ranges etc but let's leave it for later
Typo-fix in scala.concurrent.Future, thanks to @pavelpavlov