feat: use RAM/ROM opcode when supported by the backend

[guipublic]

Related issue(s)

Resolves #

Description

Summary of changes

This PR generates RAM and ROM opcodes if they are supported by the backend.
This will allow aztec backend to use UP loopk-ups for memory operations

Test additions / changes

We need a backend which support the opcodes.

Checklist

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt with default settings.
• I have linked this PR to the issue(s) that it resolves.
• I have reviewed the changes on GitHub, line by line.
• I have ensured all changes are covered in the description.

Documentation needs

• This PR requires documentation updates when merged.

[guipublic]

I don't understand why we are removing functionalities, using the proper opcode sooner is better than using a wrong one and changing it after. We want to reach an impossible target which is the backend-agnostic acir, and for what benefit?

[guipublic]

I removed the usage of is_opcode_supported() and hardcoded the barretenberg support of the memory gates instead.
Happy to revert this if we decide to!

[kevaundray]

MacOS is taking nearly 5 hours to complete -- I'm going to redo the workflow

[Savio-Sou]

Blocked by noir-lang/Planning#21.

[Savio-Sou]

Good to merge?