Support for qiskit 1.0

[bharat-thotakura]

Adds the bare minimum changes needed to support running qiskit 1.0.0

Changes in this PR:

• Updates qiskit requirement to qiskit >= 0.45.0 per comment
• Gate method updates per https://docs.quantum.ibm.com/api/migration-guides/qiskit-1.0-features#quantumcircuit-gates
• Removed QuantumCircuit.qasm per https://docs.quantum.ibm.com/api/migration-guides/qiskit-1.0-features#quantumcircuitqasm
• Removed qiskit.extensions per https://docs.quantum.ibm.com/api/migration-guides/qiskit-1.0-features#qiskitextensions

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[richrines1]

is the 1.0.0 pin necessary? it seems like all of the changes in this pr would be compatible with qiskit>=0.45.0, and the linked upgrading issues shouldn't matter if e.g. someone has 0.45.1 and wants to stay on that version

(we definitely do have to drop 0.44.* though because the qiskit.extensions gates weren't moved until 0.45.0)

[bharat-thotakura]

is the 1.0.0 pin necessary? it seems like all of the changes in this pr would be compatible with qiskit>=0.45.0, and the linked upgrading issues shouldn't matter if e.g. someone has 0.45.1 and wants to stay on that version

(we definitely do have to drop 0.44.* though because the qiskit.extensions gates weren't moved until 0.45.0)

I was thinking about dropping the qiskit-ibm-provider>=0.7.2 req actually, and it seems like we may need to because of the failing qiskit-superstaq coverage check. If we do that, then I am imagining we go back to using qiskit.qpy.dump(circuits, buf) but in light of

client-superstaq/qiskit-superstaq/qiskit_superstaq/serialization.py

Lines 114 to 117 in 3ab6c9c

	# Use `qiskit_ibm_provider.qpy` for serialization, which is a delayed copy of `qiskit.qpy`.
	# Deserialization can't be done with a QPY version older than that used for serialization, so
	# this prevents us from having to force users to update Qiskit the moment we do (this is what
	# Qiskit itself does for circuit submission)

we may want to use something like qiskit.qpy.dump(circuits, buf, version=qiskit.qpy.common.QPY_COMPATIBILITY_VERSION). But version was only added in 1.0.0 so it may cause issues for users with qiskit 0.45.1. If not, I think you're right that we should support qiskit>=0.45.0.

Edit: Looks like my concerns can be addressed by bumping to qiskit-ibm-provider>=0.9.0 and keeping qiskit>=0.45.0

[richrines1]

lgtm!