Update qpy version to terra 0.23.1

[kt474]

Summary

Updating qpy to match terra 0.23.1

co-authored by @nkanazawa1989 @jakelishman @mtreinish
Qiskit/qiskit#8278
Qiskit/qiskit#8928
Qiskit/qiskit#8927
Qiskit/qiskit#9314
Qiskit/qiskit#9002
Qiskit/qiskit#9391
Qiskit/qiskit#8949

Details and comments

[jyu00]

Let's make sure the server has 0.22 qpy before merging this.

[coveralls]

Pull Request Test Coverage Report for Build 4114740375

• 24 of 73 (32.88%) changed or added relevant lines in 6 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.2%) to 64.323%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
qiskit_ibm_runtime/qpy/type_keys.py	1	5	20.0%
qiskit_ibm_runtime/qpy/binary_io/circuits.py	12	18	66.67%
qiskit_ibm_runtime/qpy/binary_io/schedules.py	5	44	11.36%

Files with Coverage Reduction	New Missed Lines	%
qiskit_ibm_runtime/qpy/binary_io/circuits.py	2	50.52%

Totals
Change from base Build 4108438807:	0.2%
Covered Lines:	3366
Relevant Lines:	5233

---

💛 - Coveralls

[mtreinish]

You might want to pull in the fixes from 0.22.1 too, there aren't any format changes on the 0.22.x series just bugfixes for edge cases in the circuit.

[jakelishman]

If we release Terra 0.22.2 today, is that going to cause versioning issues?

[jyu00]

If we release Terra 0.22.2 today, is that going to cause versioning issues?

@jakelishman It'll be fine since qiskit-ibm-runtime uses its own copy of qpy now.

[jakelishman]

Just a note: the content of fdaa4e7 is currently tagged for Terra 0.23.0 in late January, rather than the 0.22.3 bugfix release. It's only deserialisation fixes, so it should be safe to include if you want it immediately, but we pushed it from Terra 0.22.3 because we were nervous about the scope of the change.