Do not create Subrange Assertions for the full range of an integer

[briansull]

Encountered while investigating issue #12877 and the fix dotnet/coreclr#25260

category:cq
theme:assertion-prop
skill-level:beginner
cost:small

[mikedn]

I've tried to remove those 2 TYP_INT/UINT cases to see what happens - there were a couple of diffs in a single method somewhere in System.Private.Xml. Apparently removing those leaves room for other assertions and some IND nodes end up without GTF_EXCEPT due to non-null assertions.

I suspect that those cases can be kept for casts with overflow checks but the range needs to be adjusted to be useful in any way - a cast with overflow check between TYP_INT and TYP_UINT should generate a 0..INT_MAX range assertion. Though I doubt there are many practical uses for that.