feat(test): Enable the test fuzzer for Wasm

[aakoshh]

Description

Problem*

Resolves #6738

Summary*

• Upgrades proptest to 1.6 to be able to use u128 and i128 strategies with Wasm
• Creates the UIntStrategy with max 64 bit size, still returning u128
• Creates the IntStrategy with max 64 bit size, still returning i128
• Enables the FuzzedExecutor for #[test]s with inputs on Wasm
• Disables the fork and timeout features, otherwise it doesn't seem to compile for Wasm (the compiler needs to be told if the target OS is unix or windows).

Additional Context

The ticket says:

we've since restricted the type system to only allow u64s as the maximum integer type.

I couldn't find where exactly this happened, it would be nice to include a link.

I started with using u64 instead of u128, and i64 instead of i128; the latter covers half the range as if we used u64 and mapped to negative or positive based on whether the random start value we picked was negative or positive. I did it that way because proptest enabled i128 and u128 for Wasm just last week, and I thought it would be easier to to go back to using i128 when it's released. Then I noticed that proptest 1.6 was actually just released yesterday, and it includes the above change, it just didn't have a tag in the repo 🎉

On a different note this shifting makes it look like we don't even want negative values for signed numbers, so maybe it would be easier to just use the UIntStrategy without fixtures and covert the returned value to i128.

Compilation

CI uses wasm-pack, but we can also compile it locally with:

cargo build -p noir_wasm --target wasm32-unknown-unknown

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.

[github-actions]

Peak Memory Sample

Program	Peak Memory
keccak256	78.48M
workspace	123.64M
regression_4709	422.91M
ram_blowup_regression	1.58G
private-kernel-tail	201.52M
private-kernel-reset	716.79M
private-kernel-inner	291.60M
parity-root	171.90M

[github-actions]

Compilation Report

Program	Compilation Time	%
sha256_regression	1.332s	-2%
regression_4709	0.768s	-3%
ram_blowup_regression	14.800s	-2%
rollup-root	3.940s	-6%
rollup-block-merge	4.220s	-5%
rollup-base-public	115.000s	1%
rollup-base-private	92.700s	-2%
private-kernel-tail	1.029s	-1%
private-kernel-reset	6.942s	0%
private-kernel-inner	2.036s	-4%
noir-contracts	87.400s	4%

[github-actions]

Execution Report

Program	Execution Time	%
sha256_regression	0.104s	3%
regression_4709	0.001s	0%
ram_blowup_regression	0.583s	0%
rollup-root	0.126s	1%
rollup-block-merge	0.124s	-3%
rollup-base-public	6.450s	-2%
rollup-base-private	5.750s	-1%
private-kernel-tail	0.023s	0%
private-kernel-reset	0.388s	0%
private-kernel-inner	0.116s	-2%

[github-actions]

Compilation Memory Report

Program	Peak Memory
keccak256	78.48M
workspace	123.72M
regression_4709	422.91M
ram_blowup_regression	1.58G
rollup-base-public	10.47G
rollup-base-private	6.57G
private-kernel-tail	201.79M
private-kernel-reset	717.06M
private-kernel-inner	291.86M

[github-actions]

Execution Memory Report

Program	Peak Memory
keccak256	74.61M
workspace	123.88M
regression_4709	315.92M
ram_blowup_regression	512.47M
rollup-base-public	3.05G
rollup-base-private	2.97G
private-kernel-tail	181.16M
private-kernel-reset	255.25M
private-kernel-inner	214.35M

[TomAFrench]

Nice!