fix semantic tests for max-/minInt
maxInt was one to bit, it's 2^32 / 2 - 1 == 2147483647 minInt is a bit more complicated... There are no negative integer tokens. -2147483647 is a unary minus followed by a 2147483647 integer literal but, what is -2147483648 ? -2147483648 is a unary minus followed by a 2147483648 integer literal which is out of bounds... The parser could move the minus into the integer literal, making it negative, but that would technically be constant folding and shouldn't happen at this stage.