Fix reverse_bits with registerless bits in all 3 circuit drawers

[enavarro51]

Summary

Fixes #7303

Details and comments

This PR fixes an issue with the 3 circuit drawers where the registerless bits indexing was not reversed when the reverse_bits option was used. It now correctly displays as,

bits = [Qubit(), Qubit(), Clbit(), Clbit()]
bits1 = [Clbit()]
cr = ClassicalRegister(2, "cr")
cs = ClassicalRegister(2, "cs")
qc = QuantumCircuit(bits, cr, [Clbit()], cs, bits1)
qc.h(0).c_if(4, 0)
qc.measure(0, bits[3])
qc.draw('mpl', scale=0.7,cregbundle=False, reverse_bits=True)

[coveralls]

Pull Request Test Coverage Report for Build 1830645646

• 250 of 358 (69.83%) changed or added relevant lines in 4 files are covered.
• 3 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.05%) to 83.334%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
qiskit/visualization/utils.py	55	57	96.49%
qiskit/visualization/text.py	61	75	81.33%
qiskit/visualization/latex.py	109	131	83.21%
qiskit/visualization/matplotlib.py	25	95	26.32%

Files with Coverage Reduction	New Missed Lines	%
qiskit/visualization/matplotlib.py	3	25.58%

Totals
Change from base Build 1829418994:	-0.05%
Covered Lines:	52228
Relevant Lines:	62673

---

💛 - Coveralls

[jakelishman]

Thanks for doing this - the new form looks right. The way that registers interact in the "order" with respect to loose bits is slightly unusual, but that's because of the super weird position ClassicalRegister is in right now in our data model - not the fault of this PR at all.

[enavarro51]

@jakelishman I have now deprecated qregs, cregs, global_phase, layout, and calibrations from the 3 circuit drawers and these are now set using the newly passed in circuit kwarg. If circuit is None, a new circuit is created in the __init__ of the drawer using the qubits and clbits args. I also added with_layout as a kwarg and this is used to decide whether to use the QuantumCircuit._layout or not. I believe this covers all the outstanding review issues.

[1ucian0]

Is this a deprecation warning? What is being replaced with in the future?

[1ucian0]

Thanks Edwin!