Add patch release notes and docs fixes (#1412)

### Summary

Closes #1401. Our release notes currently doesn't include notes of the
patch releases before the most recent minor release. This PR updates
`release_notes.rst` to build previous patch releases (0.3.1 isn't
rendering but I think it's too old to be useful now anyways). The new
process prior to release is that release notes from the most recent
minor version's patch releases should be deleted from the main branch
prior to a new minor release, and `release_notes.rst` needs to have a
new directive added for the previous stable branch.

### Details and comments

A few other minor changes:

- Wraps the output text of jupyter-sphinx blocks
- Update the contributor guide to include release note subcategories
- Suppress the debugger warning during the docs build by setting
`PYDEVD_DISABLE_FILE_VALIDATION=1`
- Add a link to the main branch to the dev docs banner
-

Author: coruscating

.github/workflows/docs_stable.yml

@@ -25,7 +25,7 @@ jobs:
       - name: Build docs stable
         env:
           QISKIT_DOCS_BUILD_TUTORIALS: 'always'
-        run: EXPERIMENTS_DEV_DOCS=1 PROD_BUILD=1 tox -e docs
+        run: PROD_BUILD=1 tox -e docs
       - name: Bypass Jekyll Processing # Necessary for setting the correct css path
         run: touch docs/_build/html/.nojekyll
       - name: Set current version

CONTRIBUTING.md

@@ -241,7 +241,7 @@ you aren't using and update the contents for those you are. For example, the end
 should look something like:
 
 ```yaml
-features:
+features_expclass:
   - |
     Introduced a new feature foo that adds support for doing something to
     :class:`~qiskit.circuit.QuantumCircuit` objects. It can be used by using the foo function,
@@ -272,7 +272,10 @@ deprecations:
     :func:`qiskit.bar.foobar` calls to :func:`qiskit.foo`.
 ```
 
-You can also look at existing release notes for more examples.
+Note that we are using subsections within the `features`, `upgrade`, and `fixes` sections to
+organize the notes by functional area. We strongly encourage you to file your note under the most
+appropriate category. You can see the current list of categories in
+[release_notes/config.yaml](https://github.com/Qiskit-Extensions/qiskit-experiments/blob/main/releasenotes/config.yaml).
 
 You can use any restructured text feature in them (code sections, tables, enumerated
 lists, bulleted list, etc.) to express what is being changed as needed. In general, you

docs/_static/dataframe.css renamed to docs/_static/customstyles.css

@@ -1,3 +1,9 @@
+/* Wrap text of jupyter-sphinx output blocks */
+
+div.output pre{
+    white-space: pre-wrap;
+}
+
 /* Styling for pandas dataframes in documentation */
 
 div.output table {

docs/conf.py

@@ -80,7 +80,7 @@
 templates_path = ["_templates"]
 # Manually add the gallery CSS file for now
 # TODO: Figure out why the styling is not working by default
-html_css_files = ["nbsphinx-gallery.css", "dataframe.css"]
+html_css_files = ["nbsphinx-gallery.css", "customstyles.css"]
 
 nbsphinx_timeout = 360
 nbsphinx_execute = os.getenv("QISKIT_DOCS_BUILD_TUTORIALS", "never")
@@ -176,7 +176,8 @@
 if os.getenv("EXPERIMENTS_DEV_DOCS", None):
     rst_prolog = """
 .. note::
-    This is the documentation for the current state of the development branch
+    This is the documentation for the current state of the `development branch 
+    <https://github.com/Qiskit-Extensions/qiskit-experiments/tree/main>`_
     of Qiskit Experiments. The documentation or APIs here can change prior to being
     released.
 """

docs/release_notes.rst

@@ -1 +1,9 @@
-.. release-notes:: Release Notes
+=============
+Release Notes
+=============
+
+.. release-notes::
+   :earliest-version: 0.6.0
+
+.. release-notes::
+   :branch: stable/0.5

docs/tutorials/visualization.rst

@@ -78,12 +78,6 @@ The plotter that generated the figure can be accessed through the analysis insta
 and customizing the figure can be done by setting the plotter's options. We now modify
 the color, symbols, and size of our plot, as well as change the axis labels for the amplitude units:
 
-.. jupyter-execute::
-    :hide-code:
-    :hide-output:
-
-    %matplotlib inline
-
 .. jupyter-execute::
 
     # Retrieve the plotter from the analysis instance
@@ -185,7 +179,7 @@ were styled differently according to the ``series_params`` attribute of ``figure
 
 By default, the supported figure options are ``xlabel``, ``ylabel``, ``xlim``, ``ylim``,
 ``xval_unit``, ``yval_unit``, ``xval_unit_scale``, ``yval_unit_scale``, ``xscale``, ``yscale``,
-``figure_title``, and ``series_params``; see `:class:.MplDrawer` for details on how to set these
+``figure_title``, and ``series_params``; see :class:`.MplDrawer` for details on how to set these
 options. The following T1 experiment provides examples to options that have not been demonstrated
 until now in this tutorial:
 

qiskit_experiments/framework/base_analysis.py

@@ -256,7 +256,7 @@ def _run_analysis(
 
         Returns:
             A pair ``(analysis_results, figures)`` where ``analysis_results``
-            is a list of :class:`AnalysisResultData` objects, and ``figures``
+            is a list of :class:`.AnalysisResultData` objects, and ``figures``
             is a list of any figures for the experiment.
 
         Raises:

releasenotes/config.yaml

@@ -4,7 +4,7 @@ default_branch: main
 sections:
   - [features, New Features, 1]
   - [features_expnew, New Experiments, 2]
-  - [features_explib, Experiment Library Updates, 2]
+  - [features_explib, Experiment Library Features, 2]
   - [features_expclass, Experiment Class Features, 2]
   - [features_analysis, Analysis Class Features, 2]
   - [features_expdata, Experiment Data Features, 2]