Getting invalid "Potential typo detected" warning

[Geokureli]

Brought up in the discord. Was told by @kLabz to make an issue, as this warning persists, even on their branch that was intended to fix it

class Test {
  static var ID = 0;
  
  static function main() {
    switch(SortMethod.random()) {
      case XY | ID:
        //      ^^
        // Potential typo detected (expected similar values are SortMethod.ID)
    }
  }
}

enum abstract SortMethod(Int) {
  var XY = 0;
  var ID = 1;
  
  static public function random() {
    return Math.random() < 0.5 ? ID : XY;
  }
}

[kLabz]

Actually I'm not sure this could work.
Also tested it against module_resolution branch without success, I had (little) hope some changes about type inference there would have helped.

wdyt @Simn ?

[Simn]

I think we should remove this awkward static var matching in Haxe 5. That has always been a hack, and I don't even remember why we originally introduced it.

[Simn]

Actually that isn't the problem here, the typo detection code path is entered in too many cases. It should only be triggered if we outright fail to find the identifier in question.

Note that I think it's correct to resolve the static var ID here, as per our resolution order.