chore: let simple_optimization optimize values whose dependent values changed

[asterite]

Description

Problem

No issue, just an optimization I noticed that could make the hashmap regression in #11659 go away

Summary

Compare the two commits where in the first one the poseidon2_permutation call wasn't optimized and in the second where it is.

Additional Context

User Documentation

Check one:

• No user documentation needed.
• Changes in docs/ included in this PR.
• [For Experimental Features] Changes in docs/ 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.

[aakoshh]

Nice find!

I'd still rename them to show that this is not necessarily a change, but being "tainted" by a changed instruction in their ancestry.

[github-actions]

⚠️ Performance Alert ⚠️

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

Benchmark suite	Current: f141bc7	Previous: 85aae28	Ratio
private-kernel-reset	0.053 s	0.042 s	1.26
rollup-block-root	0.003 s	0.002 s	1.50

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

CC: @TomAFrench