'/time' command does not throw errors when the values are too high

Expected behaviour

When you try to set the time to a value that’s unsupported, it should give you an error akin to “Value needs to be between 0 and 2147483647“.

What happens instead

You can set the time to values higher than 2147483647 without the command failing or giving a warning (it just caps).

You can add values higher than 2147483647 to the current time (even surpassing 2147483647, which is intentional afaik) without the command failing or giving a warning (it just caps the added value to 2147483647).

How to reproduce

• Run /time of minecraft:overworld set 999999999999999999 and notice that it’s capped to 2147483647 without throwing errors

• Run /time of minecraft:overworld add 999999999999999999 and notice that the time increased above the set limit of 2147483647, but the amount that was added was capped to 2147483647 without telling you