An attempt to make tests deterministic.

The nondeterminism presently showing itself in
presentation/implicit-member is a consequence of the
presentation compiler tests relying on details of the
behavior of toString calls. We need to stomp this out,
but it will take a while. Based on the check file
changes enclosed with this commit, this will suffice
for the presentation compiler tests. A broader assault
will have to take place, but not yet.
Merge pull request #2566 from paulp/pr/nondeterminism

An attempt to make tests deterministic.
Cleaning up isApplicable and neighbors.

I'd really like these methods to receive greater scrutiny.
To that end I'm scrutinizing them.
Cleaning crew moves down the hall.

Swabbing the decks of isAsSpecific and isApplicableSafe.
Wow isApplicableSafe, you don't really need to declare and
allocate a two-argument case class in order to manage a
second method call.
Moving on to checkBounds.

So much dust and debris, so little time.
Scrubbing up inferPolyAlternatives.

Now you can take inferPolyAlternatives home to meet your mother.
Commented out code from 2006.

Yes, 2006. Perhaps we should have a "sunset provision"
which removes commented-out code after seven years. Or even
slightly sooner.
Commented out code from 2007.

It's not exactly 2006-era code but it's still a little ripe.
Commented out code from 2008.
Annotated return type of a method.

Because nobody should have to guess a return type like
(List[Type], Array[Int], Boolean). In fact nobody should
ever experience such a return type at all.
Make cookJavaRawInfo return this.type.

A lot more useful than Unit.
Remove isPossiblyMissingArgs.

It has been hardcoded to return false for a long while anyway.
Pull some big chunks out of checkAccessible.

To streamline the essential logic.
Splashed soap and water on checkAccessible.

Yes checkAccessible, you patiently waited your turn.
Do you like your new clothes? Oh, still not clean enough?
I understand, but we must leave time for the other methods.
Now run along and check something.
Wipe some dirt off protoTypeArgs's face.

He's a good kid, even if not the most hygenic.
Tried to follow own advice with isCoercible.

Only to discover that it's really hard to move isCoercible
anywhere because it wants to call inferView which, despite its
suggestive name, is not visible in Infer. So I did what I
could and documented it a little.
Help makeFullyDefined allocate fewer ListBuffers.
Swabbing exprTypeArgs.

Oh exprTypeArgs, you will send us to the poorhouse with
your spendy ways. So many tuples have been dying needlessly.