chore(ci): Exclude enum tests from Brillig reports

[vezenovm]

Description

Problem*

In #7660 I was not getting an opcode diff that I am getting locally.

Although the CI jobs for the Brillig opcode reports are passing, we are getting this failure:

error: This requires the unstable feature 'enums' which is not enabled
   ┌─ execution_success/regression_7323/src/main.nr:5:5
   │  
 5 │ ╭     match x {
 6 │ │         1 => panic(f"Branch 1 should not be taken"),
 7 │ │         2 => panic(f"Branch 2 should not be taken"),
 8 │ │         3 => panic(f"Branch 3 should not be taken"),
 9 │ │         _ => (),
10 │ │     }
   │ ╰─────' Pass -Zenums to nargo to enable this feature at your own risk.
   │  

Here is an example from an entirely unrelated PR where we see the same failure: https://github.com/noir-lang/noir/actions/runs/13788593062/job/38562554298?pr=7659

Summary*

Exclude tests that use enums from the Brillig reports. Right now this is just regression_7323.

Additional Context

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]

Looks good!

We could also pass -Zenums to reports, though I guess it's not very useful if it's just for one regression test.

[vezenovm]

We could also pass -Zenums to reports, though I guess it's not very useful if it's just for one regression test.

Yeah that is what I thought. I also felt passing experimental flags to our tests could come in its own PR. Here I just wanted to get the reports working again.