Problem with graph in some API docs

[beckykd]

Environment

Windows - chrome

What is happening?

In these topics, the graphs / tables / images look wrong:

https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.GraphState
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.QuantumVolume
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.InnerProduct
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.InnerProductGate
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.AND
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.AndGate
https://docs.quantum.ibm.com/api/qiskit/pulse#pulse-builder
https://docs.quantum.ibm.com/api/qiskit/qiskit.transpiler.passes.DynamicalDecoupling#dynamicaldecoupling
https://docs.quantum.ibm.com/api/qiskit/qiskit.visualization.plot_histogram#qiskitvisualizationplot_histogram
https://docs.quantum.ibm.com/api/qiskit/qiskit.visualization.plot_bloch_multivector#qiskitvisualizationplot_bloch_multivector
https://docs.quantum.ibm.com/api/qiskit/qiskit.visualization.plot_state_paulivec#qiskitvisualizationplot_state_paulivec
https://docs.quantum.ibm.com/api/qiskit/qiskit.visualization.timeline_drawer#qiskitvisualizationtimeline_drawer

Examples of some of the problems:

The first column of this one is cut off:
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.QuantumVolume

Something is squished and cut off on the left in several. For example:
https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.InnerProduct

The top and bottom are cut off on this one:
https://docs.quantum.ibm.com/api/qiskit/pulse#pulse-builder

Also in the pulse file, these captions seem all squished:

The legend is cut off:

This title is cut off:

How can we reproduce the issue?

look at the above links.

What should happen?

All images should display properly.

Any suggestions?

This API doc has a similar graph that displays fine: https://docs.quantum.ibm.com/api/qiskit/qiskit.circuit.library.iqp_function

[alexanderivrii]

Thanks for opening this issue, @beckykd. Are you also planning to make a PR that fixes this?

My own guess is that the output we get using _generate_circuit_library_generalization is worse than using circuit.draw(), and we may want to change the former calls to latter ones across the board. What do you think?