Adjust the node builder compatible reference check to handle aliased tuples

[weswigham]

This check is needed to handle checking if the input node actually meets the required argument count for the target type (since in JS you can construct a type with fewer type arguments than required and you just get anys for the missing ones, and even in TS if the input has errors). Oddly enough, though, the way tuples are constructed can mean you have a reference node (for the alias) that points at another reference type (for the actual tuple) which have different type argument lists. As-is, this was disqualifying all cases like that (an alias of a tuple) from reuse (unless, by chance, the alias had the same argument count as the target tuple).