Odd type error comparing certain values (X should be Y)

https://try.haxe.org/#06dE6c4C

```haxe
function main() {
{a:1} == {a:1.0};
[1] == [1.0];
Type.getClass([1]) == Type.getClass([1.0]);
}
```
All three of these statements fail unexpectedly at compile time, with an odd error:
```
[ERROR] Test.hx:3: characters 17-20

3 | {a:1} == {a:1.0};
| ^^^
| Float should be Int

[ERROR] Test.hx:4: characters 13-16

4 | [1] == [1.0];
| ^^^
| Float should be Int

[ERROR] Test.hx:5: characters 5-47

5 | Type.getClass([1]) == Type.getClass([1.0]);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| error: Float should be Int
| have: Null>
| want: Null>
```
They stop erroring if you swap the places of `1` and `1.0`.

Seems a bit unintuitive considering all of these statements would be fine at runtime, yet the compiler disallows it.

Start by running the linked try.haxe.org reproduction and compare the three equality expressions, including the behavior when the operands are swapped. Trace the compiler's type-checking path for object literals, arrays, and Type.getClass calls. Done means these valid runtime comparisons no longer produce the reported Float should be Int error.

Written by the indexing model from the issue text.