Fix type inferencing and code navigation for Object vs Object[] method overloads

[eric-milles]

Consider the following:

import static C.m

abstract class A {
}

class C {
  static m(Object one) {}
  static m(Object[] zeroOrMore) {}
}

m()
m(null)
m(null, null)
m(new A() {})

The last method call is show as a reference to the "zero-or-more" overload when the type class of the argument is unavailable (unbuilt project). The first overload should make a better match and be the one selected.

[eric-milles]

The operating assumption is that the Object[] overload is declared after the other.