Update API dev docs (#2466)

An action recently synced the latest dev docs. This PR updates all dev
APIs that changed.
  > [!NOTE]
  > This pull request was created by a GitHub action.

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

docs/api/qiskit-ibm-runtime/dev/fake_provider.mdx

@@ -41,15 +41,16 @@ circuit.measure_all()
 circuit.draw('mpl', style="iqp")
 ```
 
-![../\_images/fake\_provider-1.png](/images/api/qiskit-ibm-runtime/dev/fake_provider-1.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/fake_provider-1.png)
 
 ```python
-# Transpile the ideal circuit to a circuit that can be directly executed by the backend
+# Transpile the ideal circuit to a circuit that can be
+# directly executed by the backend
 transpiled_circuit = transpile(circuit, backend)
 transpiled_circuit.draw('mpl', style="iqp")
 ```
 
-![../\_images/fake\_provider-2.png](/images/api/qiskit-ibm-runtime/dev/fake_provider-2.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/fake_provider-2.png)
 
 ```python
 # Run the transpiled circuit using the simulated fake backend
@@ -60,7 +61,7 @@ counts = pub_result.data.meas.get_counts()
 plot_histogram(counts)
 ```
 
-![../\_images/fake\_provider-3.png](/images/api/qiskit-ibm-runtime/dev/fake_provider-3.png)
+![\[Histogram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/fake_provider-3.png)
 
 <Admonition title="Important" type="danger">
   Please note that the simulation is done using a noise model generated from system snapshots obtained in the past (sometimes a few years ago) and the results are not representative of the latest behaviours of the real quantum system which the fake backend is mimicking. If you want to run noisy simulations to compare with the real quantum system, you should use the `qiskit_aer` library. After installation, you can follow the steps below to generate a simulator that mimics a real quantum system with the latest calibration results.
@@ -73,7 +74,8 @@ plot_histogram(counts)
   service = QiskitRuntimeService()
   backend = service.backend('ibmq_manila')
 
-  # generate a simulator that mimics the real quantum system with the latest calibration results
+  # generate a simulator that mimics the real quantum
+  # system with the latest calibration results
   backend_sim = AerSimulator.from_backend(backend)
   ```
 </Admonition>

docs/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDecoupling.mdx

@@ -8,7 +8,7 @@ python_api_name: qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDec
 
 # PadDynamicalDecoupling
 
-<Class id="qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDecoupling" isDedicatedPage={true} github="https://github.com/Qiskit/qiskit-ibm-runtime/tree/main/qiskit_ibm_runtime/transpiler/passes/scheduling/dynamical_decoupling.py#L40-L587" signature="PadDynamicalDecoupling(*args, **kwargs)" modifiers="class">
+<Class id="qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDecoupling" isDedicatedPage={true} github="https://github.com/Qiskit/qiskit-ibm-runtime/tree/main/qiskit_ibm_runtime/transpiler/passes/scheduling/dynamical_decoupling.py#L40-L589" signature="PadDynamicalDecoupling(*args, **kwargs)" modifiers="class">
   Bases: [`BlockBasePadder`](qiskit_ibm_runtime.transpiler.passes.scheduling.BlockBasePadder "qiskit_ibm_runtime.transpiler.passes.scheduling.block_base_padder.BlockBasePadder")
 
   Dynamical decoupling insertion pass for IBM dynamic circuit backends.
@@ -45,7 +45,7 @@ python_api_name: qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDec
   circ_dd.draw('mpl', style="iqp")
   ```
 
-  ![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-PadDynamicalDecoupling-1.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-PadDynamicalDecoupling-1.png)
+  ![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-PadDynamicalDecoupling-1.png)
 
   ```python
   # Uhrig sequence on qubit 0
@@ -67,7 +67,7 @@ python_api_name: qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDec
   circ_dd.draw('mpl', style="iqp")
   ```
 
-  ![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-PadDynamicalDecoupling-2.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-PadDynamicalDecoupling-2.png)
+  ![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-PadDynamicalDecoupling-2.png)
 
   <Admonition title="Note" type="note">
     You need to call [`ALAPScheduleAnalysis`](qiskit_ibm_runtime.transpiler.passes.scheduling.ALAPScheduleAnalysis "qiskit_ibm_runtime.transpiler.passes.scheduling.ALAPScheduleAnalysis") before running dynamical decoupling to guarantee your circuit satisfies acquisition alignment constraints for dynamic circuit backends.

docs/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime.transpiler.passes.scheduling.mdx

@@ -17,7 +17,7 @@ python_api_name: qiskit_ibm_runtime.transpiler.passes.scheduling
 A collection of scheduling passes for working with IBM Quantum’s next-generation backends that support advanced “dynamic circuit” capabilities. Ie., circuits with support for classical control-flow/feedback based off of measurement results.
 
 <Admonition title="Warning" type="caution">
-  You should not mix these scheduling passes with Qiskit’s builtin scheduling passes as they will negatively interact with the scheduling routines for dynamic circuits. This includes setting `scheduling_method` in [`transpile()`](/api/qiskit/compiler#qiskit.compiler.transpile "(in Qiskit v1.3)") or [`generate_preset_pass_manager()`](/api/qiskit/transpiler_preset#qiskit.transpiler.preset_passmanagers.generate_preset_pass_manager "(in Qiskit v1.3)").
+  You should not mix these scheduling passes with Qiskit’s built in scheduling passes as they will negatively interact with the scheduling routines for dynamic circuits. This includes setting `scheduling_method` in [`transpile()`](/api/qiskit/compiler#qiskit.compiler.transpile "(in Qiskit v1.3)") or [`generate_preset_pass_manager()`](/api/qiskit/transpiler_preset#qiskit.transpiler.preset_passmanagers.generate_preset_pass_manager "(in Qiskit v1.3)").
 </Admonition>
 
 ## Classes
@@ -80,7 +80,7 @@ scheduled_teleport = pm.run(teleport)
 scheduled_teleport.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-1.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-1.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-1.png)
 
 Instead of padding with delays we may also insert a dynamical decoupling sequence using the [`PadDynamicalDecoupling`](qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDecoupling "qiskit_ibm_runtime.transpiler.passes.scheduling.PadDynamicalDecoupling") pass as shown below:
 
@@ -105,7 +105,7 @@ dd_teleport = pm.run(teleport)
 dd_teleport.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-2.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-2.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-2.png)
 
 When compiling a circuit with Qiskit, it is more efficient and more robust to perform all the transformations in a single transpilation. This has been done above by extending Qiskit’s preset pass managers. For example, Qiskit’s [`transpile()`](/api/qiskit/compiler#qiskit.compiler.transpile "(in Qiskit v1.3)") function internally builds its pass set by using [`generate_preset_pass_manager()`](/api/qiskit/transpiler_preset#qiskit.transpiler.preset_passmanagers.generate_preset_pass_manager "(in Qiskit v1.3)"). This returns instances of [`StagedPassManager`](/api/qiskit/qiskit.transpiler.StagedPassManager "(in Qiskit v1.3)"), which can be extended.
 
@@ -121,7 +121,7 @@ qc_c_if.x(0).c_if(0, 1)
 qc_c_if.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-3.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-3.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-3.png)
 
 The [`IBMBackend`](qiskit_ibm_runtime.IBMBackend "qiskit_ibm_runtime.IBMBackend") configures a translation plugin `IBMTranslationPlugin` to automatically apply transformations and optimizations for IBM hardware backends when invoking [`transpile()`](/api/qiskit/compiler#qiskit.compiler.transpile "(in Qiskit v1.3)"). This will automatically convert all old style `c_if` conditioned gates to new-style control-flow. We may then schedule the transpiled circuit without further modification.
 
@@ -141,7 +141,7 @@ qc_if_dd = pm.run(qc_c_if, backend)
 qc_if_dd.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-4.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-4.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-4.png)
 
 If you are not using the transpiler plugin stages to work around this please manually run the pass [`qiskit.transpiler.passes.ConvertConditionsToIfOps`](/api/qiskit/qiskit.transpiler.passes.ConvertConditionsToIfOps "(in Qiskit v1.3)") prior to your scheduling pass.
 
@@ -161,7 +161,7 @@ qc_if_dd = pm.run(qc_c_if)
 qc_if_dd.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-5.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-5.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-5.png)
 
 <span id="exploiting-ibm-backend-s-local-parallel-fast-path" />
 
@@ -184,7 +184,7 @@ with qc.if_test((1, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-6.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-6.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-6.png)
 
 The circuit below will not use the fast-path as the conditional gate is on a different qubit than the measurement qubit.
 
@@ -197,7 +197,7 @@ with qc.if_test((0, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-7.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-7.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-7.png)
 
 Similarly, the circuit below contains gates on multiple qubits and will not be performed using the fast-path.
 
@@ -211,7 +211,7 @@ with qc.if_test((0, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-8.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-8.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-8.png)
 
 A fast-path block may contain multiple gates as long as they are on the fast-path qubit. If there are multiple fast-path blocks being performed in parallel each block will be padded out to the duration of the longest block.
 
@@ -229,7 +229,7 @@ with qc.if_test((1, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-9.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-9.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-9.png)
 
 This behavior is also applied to the else condition of a fast-path eligible branch.
 
@@ -246,7 +246,7 @@ with else_:
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-10.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-10.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-10.png)
 
 If a single measurement result is used with several conditional blocks, if there is a fast-path eligible block it will be applied followed by the non-fast-path blocks which will execute with the standard higher latency conditional branch.
 
@@ -264,7 +264,7 @@ with qc.if_test((0, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-11.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-11.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-11.png)
 
 If you wish to prevent the usage of the fast-path you may insert a barrier between the measurement and the conditional branch.
 
@@ -279,7 +279,7 @@ with qc.if_test((0, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-12.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-12.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-12.png)
 
 Conditional measurements are not eligible for the fast-path.
 
@@ -293,7 +293,7 @@ with qc.if_test((0, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-13.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-13.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-13.png)
 
 Similarly nested control-flow is not eligible.
 
@@ -309,7 +309,7 @@ with qc.if_test((0, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-14.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-14.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-14.png)
 
 The scheduler is aware of the fast-path behavior and will not insert delays on idle qubits in blocks that satisfy the fast-path conditions so as to avoid preventing the backend compiler from performing the necessary optimizations to utilize the fast-path. If there are fast-path blocks that will be performed in parallel they currently *will not* be padded out by the scheduler to ensure they are of the same duration in Qiskit
 
@@ -330,7 +330,7 @@ with qc.if_test((1, 1)):
 qc.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-15.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-15.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-15.png)
 
 ```python
 dd_sequence = [XGate(), XGate()]
@@ -346,7 +346,7 @@ qc_dd = pm.run(qc)
 qc_dd.draw(output="mpl", style="iqp")
 ```
 
-![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-16.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-16.png)
+![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-16.png)
 
 <Admonition title="Note" type="note">
   If there are qubits that are *not* involved in a fast-path decision it is not currently possible to use them in a fast-path branch in parallel with the fast-path qubits resulting from a measurement. This will be revised in the future as we further improve these capabilities.
@@ -370,6 +370,6 @@ qc_dd.draw(output="mpl", style="iqp")
   qc.draw(output="mpl", style="iqp")
   ```
 
-  ![../\_images/qiskit\_ibm\_runtime-transpiler-passes-scheduling-17.png](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-17.png)
+  ![\[Circuit diagram output by the previous code.\]](/images/api/qiskit-ibm-runtime/dev/qiskit_ibm_runtime-transpiler-passes-scheduling-17.png)
 </Admonition>
 

docs/api/qiskit/dev/qiskit.transpiler.passes.Decompose.mdx

@@ -8,7 +8,7 @@ python_api_name: qiskit.transpiler.passes.Decompose
 
 # Decompose
 
-<Class id="qiskit.transpiler.passes.Decompose" isDedicatedPage={true} github="https://github.com/Qiskit/qiskit/tree/main/qiskit/transpiler/passes/basis/decompose.py#L30-L122" signature="qiskit.transpiler.passes.Decompose(*args, **kwargs)" modifiers="class">
+<Class id="qiskit.transpiler.passes.Decompose" isDedicatedPage={true} github="https://github.com/Qiskit/qiskit/tree/main/qiskit/transpiler/passes/basis/decompose.py#L32-L130" signature="qiskit.transpiler.passes.Decompose(*args, **kwargs)" modifiers="class">
   Bases: [`TransformationPass`](qiskit.transpiler.TransformationPass "qiskit.transpiler.basepasses.TransformationPass")
 
   Expand a gate in a circuit using its decomposition rules.
@@ -70,7 +70,7 @@ python_api_name: qiskit.transpiler.passes.Decompose
 
   ### run
 
-  <Function id="qiskit.transpiler.passes.Decompose.run" github="https://github.com/Qiskit/qiskit/tree/main/qiskit/transpiler/passes/basis/decompose.py#L51-L92" signature="run(dag)">
+  <Function id="qiskit.transpiler.passes.Decompose.run" github="https://github.com/Qiskit/qiskit/tree/main/qiskit/transpiler/passes/basis/decompose.py#L53-L100" signature="run(dag)">
     Run the Decompose pass on dag.
 
     **Parameters**