chore(fuzz): Consider RangeCheckFailed equivalent to ConstantDoesNotFitType if the value matches

[aakoshh]

Description

Problem*

Resolves #8863

Summary*

Relaxes the Comparable implementation for the SSA interpreter errors to consider the errors from a range check equivalent to the internal error we get when a constant does not fit into the intended type, as long as the value they mention is the same. This is because SSA passes might reorder some instructions that result in failure for the same reason, but with a different manifestation in the interpreter depending on which instruction comes first.

Additional Context

This is a follow up for the discussion in #8910 without going all the way to consider every failure equivalent. That would be too aggressive at the moment, because the SSA interpreter doesn't handle prints yet (I'll do that next).

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.

[asterite]

I wonder if we should add an option to nargo interpret to check that every pass gives the "same" result. Then we could add a test program for #8863 and always pass that flag when running tests. What do you think?

[asterite]

Ah, I now realize it would be a compile_failure test for the interpret, so something new... probably for an optional follow-up PR.

[aakoshh]

It's not unheard of for the interpreter to heal itself, we could definitely add something to the interpreter command as a follow up 👍