fix(fuzz): Do not access arrays with &mut inside if using dynamic condition

[aakoshh]

Description

Problem*

Resolves #9035

Summary*

• Add an in_dynamic flag to the AST generator which is turned on when we are inside the then or the else of an if statement where the condition is using a dynamic variable. Under such circumstances anything we do inside is under some predicate that will tie the outcome to the circuit inputs in ACIR.
• Do not use arrays with references in them if we are in an in_dynamic region.
• Move the DIE post-check to happen as the last step of the SSA pipeline, to let the dynamic index access verifier provide better feedback than what the panic does.

Waiting on #9047

Additional Context

Instead of panicking on leftover loads, we can defer it to runtime using #8943
Or we can keep panicking and try to turn those panics into better user errors, like the verify_no_dynamic_indices_to_references, once we have examples of them.

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 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: c6d667a	Previous: 441f39a	Ratio
test_report_zkpassport_noir_rsa_	1 s	0 s	+∞

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: ca0f12b	Previous: 077bb6d	Ratio
rollup-block-root-single-tx	227 s	185 s	1.23

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

CC: @TomAFrench

[asterite]

Looks good! I left a question but it's likely me misunderstanding.