Consider updating symengine pin

[bharat-thotakura]

What is happening?

We currently pin symengine~=0.11.0 after #874 in the requirements of qiskit-superstaq. However, that version seems to have issues building a wheel in a Python 3.13 environment, so we should pin the recently released v0.13.0 which installs as expected (and since qiskit>=1.0.0 supports symengine>=0.11).

Any additional context?

qiskit-superstaq version: 0.5.27
qiskit version: 1.2.2
Python version: 3.13.0rc2
Operating system: Ubuntu

[bharat-thotakura]

Related: Qiskit/qiskit#13251

[jakelishman]

Also Qiskit/qiskit#13259 - we borked the 1.2.3 release by being in too much of a rush, and yanked it. We'll make 1.2.4 shortly (tomorrow, most likely), which should be ok for any combination of symengine 0.11 and 0.13 between client and server, since ParameterExpression should limit our exposure to the full set of changes in symengine between those versions.

We hadn't come across the problem before, but it looks like you guys did in #874. We'll be working on reducing our dependence on symengine in the future. Near-term, we're hoping to cut it out of serialisation (Qiskit/qiskit#13252), and longer term, potentially remove the dependence entirely.

[vtomole]

@natibek Run a basic submission locally after updating this pin to make sure roundtrip serialization works.

[natibek]

Closed with #1097