fix: use predicate expression as binary result

[guipublic]

Description

Problem*

Resolves #8558

Summary*

Use the predicate expression computed for disabling overflow checks as the result of binary operations.

Additional Context

Truncation is not using the predicate because a constant division is not expected to fail.
However predicated computations can overflow and underflow because the over/under_flow checks are disabled when the predicate is false, which can result in failing range checks.
Rather than fixing those by using the predicate, it is simpler to use the predicated expression, already computed for disabling the overflow checks. That way, we do not need to predicate further range checks.
This should enable the simplification of some predicate checks, e.g in euclidian division.

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]

Changes to circuit sizes

Generated at commit: 26b860ea2f414936f50492336d4a9de79afe2224, compared to commit: 0112e2197c2a2067d950bf45740d0946bbf75e9c

🧾 Summary (10% most significant diffs)

Program	ACIR opcodes (+/-)	%	Circuit size (+/-)	%
conditional_1	-55 ✅	-2.05%	-59 ✅	-0.73%
regression_8329	-3 ✅	-7.69%	-3 ✅	-5.45%

---

Full diff report 👇

Program	ACIR opcodes (+/-)	%	Circuit size (+/-)	%
slices	670 (+2)	+0.30%	3,769 (+2)	+0.05%
regression_3607	37 (0)	0.00%	2,800 (+1)	+0.04%
hashmap	33,473 (+4)	+0.01%	94,508 (+4)	+0.00%
slice_dynamic_index	812 (0)	0.00%	6,464 (-1)	-0.02%
conditional_1	2,633 (-55)	-2.05%	7,987 (-59)	-0.73%
regression_8329	36 (-3)	-7.69%	52 (-3)	-5.45%