chore!: backend can specify which opcode they support

[guipublic]

Description

Summary of changes

replace blackbox_supported with opcode_supported

Dependency additions / changes

(If applicable.)

Test additions / changes

(If applicable.)

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.

Additional context

This is useful for memory opcodes, we could have a TP backend which supports only ROM opcode for instance.

[TomAFrench]

Can you address the other point in #183 in this PR?

[guipublic]

Can you address the other point in #183 in this PR?

I was addressing them directly in #183

[TomAFrench]

Sorry I don't follow, can you clarify what you mean? This PR as it is won't allow us to pass backend.opcode_supported into acvm::compile

[guipublic]

Sorry I don't follow, can you clarify what you mean? This PR as it is won't allow us to pass backend.opcode_supported into acvm::compile

My bad, I thought you were talking about PR 153 on aztec backend (not the same repo and even not the same number...), sorry for the confusion.
I will look at the issue 183.

[TomAFrench]

Closing in favour of #273