This will result in the diff in
#558 being more focused.

This also adds missing methods/attributes thanks to @arnaucasau's bug
fix in #552.

This uses the latest builds from the stable/0.14 and stable/0.15
branches. I suspect #552
might explain why 0.14 changed.

```
npm run gen-api -- -p qiskit-ibm-runtime -v 0.14.0 --historical -a https://github.com/Qiskit/qiskit-ibm-runtime/actions/runs/6806114640/artifacts/1038218994
npm run gen-api -- -p qiskit-ibm-runtime -v 0.15.0 --historical -a https://github.com/Qiskit/qiskit-ibm-runtime/actions/runs/6908950459/artifacts/1058131555
```

Part of #495. We now will
enforce in CI that historical API docs are valid for Runtime and
Provider. To do this, this PR adds the `--skip-broken-historical`
argument.

In a follow up, I want to try checking Qiskit docs, at least certain
versions. But I'm waiting until we regenerate the docs with
#552 applied because I
suspect it will fix some issues.

Part of #495. We now will
enforce in CI that historical API docs are valid for Runtime and
Provider. To do this, this PR adds the `--skip-broken-historical`
argument.

In a follow up, I want to try checking Qiskit docs, at least certain
versions. But I'm waiting until we regenerate the docs with
#552 applied because I
suspect it will fix some issues.

The generation script was not inlining all the methods in the class
pages because we weren't assigning the correct value to the
`python_api_name` metadata. With this PR, we change the way we search
for the id we set as the name in the `sphinxHtmlToMarkdown.ts`

The problem comes from we are missing the class `sig-object` in the `dt`
tags we used to extract the `python_api_name` metadata in the HTML used
to generate the markdown API files. We actually don't need to specify
the class because the `dt` tag we are looking for is unique, and this PR
fixes that.

Moreover, the changes introduced in Qiskit#543 are reverted to recover the
mergeClassMembers.ts script that we need to inline all the methods in
historical versions.

Tested the generation of Qiskit 0.33, where we will inline the methods
in a follow-up, and also the generation of Qiskit 0.45 to validate we
are not modifying any version that was working previously.

Commands used (Notice we need to have the API docs downloaded in .out):

> npm run gen-api -- -p qiskit -v 0.33.0 -a "" --historical
> npm run gen-api -- -p qiskit -v 0.45.0 -a ""

Part of Qiskit#542

This will result in the diff in
Qiskit#558 being more focused.

This also adds missing methods/attributes thanks to @arnaucasau's bug
fix in Qiskit#552.

This uses the latest builds from the stable/0.14 and stable/0.15
branches. I suspect Qiskit#552
might explain why 0.14 changed.

```
npm run gen-api -- -p qiskit-ibm-runtime -v 0.14.0 --historical -a https://github.com/Qiskit/qiskit-ibm-runtime/actions/runs/6806114640/artifacts/1038218994
npm run gen-api -- -p qiskit-ibm-runtime -v 0.15.0 --historical -a https://github.com/Qiskit/qiskit-ibm-runtime/actions/runs/6908950459/artifacts/1058131555
```

Part of Qiskit#495. We now will
enforce in CI that historical API docs are valid for Runtime and
Provider. To do this, this PR adds the `--skip-broken-historical`
argument.

In a follow up, I want to try checking Qiskit docs, at least certain
versions. But I'm waiting until we regenerate the docs with
Qiskit#552 applied because I
suspect it will fix some issues.