Fix priority for classinfos in is a ... comparison.

[Moderocky]

Some existing (and a lot of upcoming) syntax have an expression that is the same as their type name: a queue, a scoreboard, a team, a task, , etc.

We're trying to eliminate the necessity of new in these patterns (e.g. it's okay to do set {x} to a queue rather than set {x} to a new queue) but the current limitation is that comparison conditions, e.g. if {x} is a queue will always parse as the wrong thing, since the expression is checked before the classinfo.
This means that they parse as if <x> is <a new X expression> rather than if <x> is a <X classinfo>.

Ideally, we want to fix this comparison or at least find a nicer way of resolving the conflict.

I'm leaving this here as a todo and so that we have something to refer to when reviewing the PRs for syntax like this in the future.