chore(ACIR): more consistent syntax and with less noise

[asterite]

Description

Problem

No issue, just the last follow-up to improve ACIR syntax.

Summary

Several commits here:

1. current witness is no longer printed. I think this is fine but let me know otherwise. We still need to set one when constructing the circuit: we use the maximum witness we find during parsing.
2. Some ACIR used "PREDICATE" (uppercase) and I thought this wasn't consistent with everything else so I changed it to lowercase
3. There was an inconsistency when displaying opcodes with "arguments". We usually show them as "OP arg1: value1, arg2: value2, etc.` but this wasn't true in all cases, but now it is.
4. The previous point was also applied to blackboxes, where it had a syntax like [...]:N [] where the first array are the inputs, the ":N" is a bitsize and the last "[]" are the outputs. Now it's shown as inputs: [...], bits: ..., outputs: ...
5. The range blackbox only has one input and has no outputs: we use a simpler syntax here (less noise, and no possibility of error since we have to pass one input and we don't expect ouptuts)
6. Similarly, some blackboxes only had one output and now that's displayed/parsed like that
7. Memory ops have been revamped. Now they look more like array operations:
   • `INIT b0 = [w1, w2]
   • READ w3 = b0[w4]
   • WRITE b0[w5] = w6
     But let me know if this is too much.
8. Use CONSTRAIN instead of EXPR to make it clear that = there isn't an assignment.

Additional Context

This is the last change I had in mind for ACIR (🤞) as now it looks pretty well and consistent.

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]

⚠️ Performance Alert ⚠️

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

Benchmark suite	Current: b6cd350	Previous: 6898710	Ratio
rollup-checkpoint-merge	0.004 s	0.003 s	1.33
sha512-100-bytes	0.097 s	0.054 s	1.80

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

CC: @TomAFrench

[github-actions]

⚠️ Performance Alert ⚠️

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

Benchmark suite	Current: e92d316	Previous: 5bf9bc2	Ratio
test_report_zkpassport_noir-ecdsa_	3 s	1 s	3

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

CC: @TomAFrench

[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: 9ef120e	Previous: cb5c0ed	Ratio
private-kernel-reset	9.224 s	7.564 s	1.22

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

CC: @TomAFrench

[vezenovm]

Overall looks good! Just a couple nits

[vezenovm]

Will probably have some test failures post #10017