Fixes type range issue during linting (#16684)

[robertg]

• Ensures the propagated negation sign is properly utilized during type checking.
• Combines Add failing testcase, issue #16684 #16962, Closes i64::MIN literal out of range warning #16684.

[robertg]

When I run make check, the type bounds tests fail, such as:

/users/rdgawdzi/dev/rust/src/test/compile-fail/lint-type-overflow.rs:57:14: 57:41 error: literal out of range for its type
/users/rdgawdzi/dev/rust/src/test/compile-fail/lint-type-overflow.rs:57     let x =  1.7976931348623159e+308_f64; //~ error: literal out of range for its type

This is a good thing judging by the comments, but should these tests be rewritten so the error is actually handled, and the build passes?

[alexcrichton]

Could you add a test for #16684? Also yes, the tests will need to be fixed before landing.

[robertg]

I will merge in and combine #16962, which adds a test for the fix, but the build failed because I wasn't converting the min/max range properly to positive: (since: i8::MIN as u64 // => 18446744073709551488)

[robertg]

The tests now pass: test [compile-fail] compile-fail/lint-type-overflow.rs ... ok