cut-huge-range.sh: make cut fails on usize::MAX

[sylvestre]

GNU fails with
$ cut -b18446744073709551615 /dev/null
but we are able to support this value

we both fail with
$ cut -b18446744073709551616 /dev/null

[github-actions]

GNU testsuite comparison:

Congrats! The gnu test tests/misc/cut-huge-range is no longer failing!

[cakebaker]

What's the reason to adjust the test instead of our code?

[tertsdiepraam]

My theory for why we support this and GNU doesn't is that we might be using an inclusive range internally and that GNU would be using an exclusive range internally, parsed from an inclusive range.

If everything else works as expected I don't see a reason explicitly break support for that single value.

For context, though that might be obvious, the value in the GNU test is u64::MAX. Using an exclusive range with a u64 would mean that the largest value in that range is u64::MAX - 1. With an inclusive range it's u64::MAX.

[sylvestre]

Honestly, I don't know why it is done this way.

I am not sure how to update the parsing code to do this:

coreutils/src/uucore/src/lib/mods/ranges.rs

Line 39 in d02bd2f

fn from_str(s: &str) -> Result<Self, &'static str> {

[sylvestre]

not sure why github action didn't comment but it passes:
2023-09-24T21:59:28.7735199Z PASS: tests/cut/cut-huge-range.sh