#5295: reject out-of-int-range numbers in Expect.Int and Expect.Natural

[morphqdd]

Closes #5295.

Expect.Int.it() and Expect.Natural.it() narrow a Double to Integer via Double::intValue
without first checking the value fits in int range. Double.intValue() doesn't throw for a
value outside int range — it saturates, returning Integer.MAX_VALUE/Integer.MIN_VALUE. Since
the saturated value is still a "valid" integer (and, for Natural, still >= 0), no downstream
check catches it, e.g. malloc.of 1000000000000000 silently allocates a 2147483647-byte block
instead of raising a domain error for a size nowhere near what was requested.

Added a must step before the Double::intValue narrowing in both Expect.Int and
Expect.Natural that rejects any value outside [Integer.MIN_VALUE, Integer.MAX_VALUE] with a
"must fit into int range" message, matching the existing style of this validation pipeline
(must be an integer, must be greater or equal to zero).

Added two tests in ExpectTest (failsInTransformingToIntegerForTooLarge,
failsInTransformingToNonNegativeIntegerForTooLarge) mirroring the existing
failsInTransformingTo...ForNotInteger/ForNegative tests, using 1.0e15 as the out-of-range
value from the issue's reproduction.

Ran the full Expect-related test suite locally (ExpectTest, EOmallocAllocatedExpectTest,
EOmallocWritePhiExpectTest, EOiConvertersExpectTest, EObytesEOrightExpectTest,
EOi64ExpectTest) — all 36 tests pass.

[github-actions]

🚀 Performance Analysis

All benchmarks are within the acceptable range. No critical degradation detected (threshold is 100%). Please refer to the detailed report for more information.

Click to see the detailed report

Test	Base Score	PR Score	Change	% Change	Unit	Mode
benchmarks.XmirBench.xmirToEO	10803.912	10940.517	136.606	1.26%	ms/op	Average Time

⚠️ Performance loss: benchmarks.XmirBench.xmirToEO is slower by 136.606 ms/op (1.26%)

[morphqdd]

@yegor256, please take a look when you have a moment.

[morphqdd]

@yegor256, please take a look when you have a moment.

[yegor256]

@morphqdd https://www.yegor256.com/2014/06/19/avoid-string-concatenation.html

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[0crat]

@yegor256 Thanks for the review! You've earned +7 points for this: +12 as a basis; -5 for very few (1) comments. Your running score is +1695; don't forget to check your Zerocracy account too).

[0crat]

@morphqdd Thanks for the contribution! You've earned +16 points. Please, keep them coming. Your running score is +640; don't forget to check your Zerocracy account too).