Attributes with incomplete signatures for some versions of qiskit

[arnaucasau]

There are some attributes in the qiskit API docs with incomplete signatures. We can find two examples in qiskit 0.19 at BaseSchema and FlowController.

For the former, we can see how the attribute TYPE_MAPPING and opts don't have a correct default value:

These attributes seem to correspond to the Schema class of the marshmallow library (search for TYPE_MAPPING on this page). In the next screenshot we can see how the signature would look like without processing it with a unified plugin like in the API generation script and instead using $child.text():

In the previous screenshot we can see also one attribute from the FlowController class which in some versions like 0.40, has that exact value:

We should figure out why sometimes these signatures are incomplete for some versions. One solution to explore would be to remove the unified plugin used in generateApiComponents.ts and replace it with $child.text(), making sure we espace the apostrophes and double quotes symbols of the signature.

[Eric-Arellano]

@arnaucasau this can be fixed by manually fixing the HTML as part of #1252, right? If so, can you please close this as "not planned"?

[arnaucasau]

I think we can maybe fix both issues by only changing our script and not the HTML. The result simplifies the script instead of making it more complex. I created a draft PR with a possible fix here.