fix!: check abi integer input is within signed range

[asterite]

Description

Problem

Resolves #7304

Summary

I accidentally started fixing this when parsing strings, but I think that's also good to have. (edit: it turns out the original issue was about strings 😅)

Then I added a similar check for integers... though here we only need to check the maximum value because input values are always unsigned (is there a reason for this? -> this PR now also allows negative integers in at least Prover.toml (I hope that's fine!)).

Finally, I noticed that the error message produced in this case was very barebones: it didn't mention which parameter name errored. So now that's shown, and also if the value is inside an array, that index is shown (a similar thing is done for tables where we show which field we are in).

The error shown for the program in #7304 is now this:

The value passed for parameter `x` is invalid:
Value 200 exceeds maximum value of 127

Additional Context

Documentation

Check one:

• No documentation needed.
• Documentation included in this PR.
• [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[asterite]

Hm, it seems the behavior before this PR was maybe expected:

https://github.com/noir-lang/noir/tree/master/test_programs/execution_success/signed_cmp

Maybe because there's no way to pass negative integers otherwise (well, you could use a string).

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Compilation Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 37a0567	Previous: 819a53a	Ratio
rollup-block-root	90.4 s	70 s	1.29

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

[michaeljklein]

LGTM, though just noticed that InputExceedsMinimum sounds like min < input instead of the intended input < min (not blocking).