Update mlir version to have closure-aware backward slice

[paul0403]

Context:
Proposal: we update the mlir commit we track to see llvm/llvm-project#114452

When using backward slice to track def-use chains, sometimes there are closure variables not explicitly visible as an operand, e.g.

    %7 = quantum.insert %5[%2], %out_qubits : !quantum.reg, !quantum.bit
    %8 = scf.if %1 -> (!quantum.reg) {
      %15 = quantum.extract %7[ 0] : !quantum.reg -> !quantum.bit
      %out_qubits_5 = quantum.custom "RZ"(%cst_1) %15 : !quantum.bit
      %16 = quantum.insert %7[ 0], %out_qubits_5 : !quantum.reg, !quantum.bit
      scf.yield %16 : !quantum.reg
    } else {
      scf.yield %7 : !quantum.reg
    }
    %9 = quantum.extract %8[%0] : !quantum.reg -> !quantum.bit
    %10 = quantum.extract %8[ 1] : !quantum.reg -> !quantum.bit
    %out_qubits_4:2 = quantum.custom "CNOT"() %9, %10 : !quantum.bit, !quantum.bit
    %11 = quantum.insert %8[%0], %out_qubits_4#0 : !quantum.reg, !quantum.bit

when running backward slice on %11 to track all necessary previous values that dominate %11, the current mlir commit we track cannot detect %7, because %7 is not an explicit operand of the scf.if op, but implicitly captured by region closure. The proposed commit to track adds a new option, omitUsesFromAbove , to the mlir backward slice analysis, and can be turned off to include clousure variables.

Description of the Change:
Update the mlir commit we track

Benefits:
New mlir features available

Possible Drawbacks:
Updating versions might break things

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/releases/changelog-dev.md on your branch with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[dime10]

Have you tested locally? Not sure where exactly this commit is, but MLIR deprecated the old bufferization functions which we were working on replacing to be able to update.

Also, normally the llvm commit is matched exactly to the JAX dependency.

[paul0403]

Have you tested locally? Not sure where exactly this commit is, but MLIR deprecated the old bufferization functions which we were working on replacing to be able to update.

Also, normally the llvm commit is matched exactly to the JAX dependency.

I haven't tried locally, I wanted to use CI to see what happens. I am aware of the two points you mentioned here so I am not super in favor of this update either, but I just wanted to see how much work would be necessary if we did want to update, comparing with writing the described functionality ourselves.

[paul0403]

Ok I think the update might be too much, we can just write this simple functionality ourselves for this one purpose :)

Although on the other hand, an argument can be made that we should update dependencies more often to catch errors early?

[paul0403]

Closing as we have other schedules for llvm version updates.

Also, this functionality is no longer necessary, as the original feature that requested this was implemented by another design.