Docs: Replace Recommonmark with MyST Parser

Recommonmark has been deprecated since 2021 [1] and the last release was
over 3 years ago [2]. As per their announcement, Markedly Structured
Text (MyST) Parser [3] is the recommended replacement.

For the most part, the existing documentation is compatible with MyST,
as both parsers are built around the CommonMark flavor of Markdown. The
main difference that affects coreboot is how the Sphinx toctree is
generated. Recommonmark has a feature called auto_toc_tree, which
converts single level lists of references into a toctree:

* [Part 1: Starting from scratch](part1.md)
* [Part 2: Submitting a patch to coreboot.org](part2.md)
* [Part 3: Writing unit tests](part3.md)
* [Managing local additions](managing_local_additions.md)
* [Flashing firmware](flashing_firmware/index.md)

MyST Parser does not provide a replacement for this feature, meaning the
toctree must be defined manually. This is done using MyST's syntax for
Sphinx directives:

```{toctree}
:maxdepth: 1

Part 1: Starting from scratch <part1.md>
Part 2: Submitting a patch to coreboot.org <part2.md>
Part 3: Writing unit tests <part3.md>
Managing local additions <managing_local_additions.md>
Flashing firmware <flashing_firmware/index.md>
```

Internally, auto_toc_tree essentially converts lists of references into
the Sphinx toctree structure that the MyST syntax above more directly
represents.

The toctrees were converted to the MyST syntax using the following
command and Python script:

`find ./ -iname "*.md" | xargs -n 1 python conv_toctree.py`

```
import re
import sys

in_list = False
f = open(sys.argv[1])
lines = f.readlines()
f.close()

with open(sys.argv[1], "w") as f:
    for line in lines:
        match = re.match(r"^[-*+] \[(.*)\]\((.*)\)$", line)
        if match is not None:
            if not in_list:
                in_list = True
                f.write("```{toctree}\n")
                f.write(":maxdepth: 1\n\n")
            f.write(match.group(1) + " <" + match.group(2) + ">\n")
        else:
            if in_list:
                f.write("```\n")
            f.write(line)
            in_list = False

    if in_list:
        f.write("```\n")
```

While this does add a little more work for creating the toctree, this
does give more control over exactly what goes into the toctree. For
instance, lists of links to external resources currently end up in the
toctree, but we may want to limit it to pages within coreboot.

This change does break rendering and navigation of the documentation in
applications that can render Markdown, such as Okular, Gitiles, or the
GitHub mirror. Assuming the docs are mainly intended to be viewed after
being rendered to doc.coreboot.org, this is probably not an issue in
practice.

Another difference is that MyST natively supports Markdown tables,
whereas with Recommonmark, tables had to be written in embedded rST [4].
However, MyST also supports embedded rST, so the existing tables can be
easily converted as the syntax is nearly identical.

These were converted using
`find ./ -iname "*.md" | xargs -n 1 sed -i "s/eval_rst/{eval-rst}/"`

Makefile.sphinx and conf.py were regenerated from scratch by running
`sphinx-quickstart` using the updated version of Sphinx, which removes a
lot of old commented out boilerplate. Any relevant changes coreboot had
made on top of the previous autogenerated versions of these files were
ported over to the newly generated file.

From some initial testing the generated webpages appear and function
identically to the existing documentation built with Recommonmark.

TEST: `make -C util/docker docker-build-docs` builds the documentation
successfully and the generated output renders properly when viewed in
a web browser.

[1] https://github.com/readthedocs/recommonmark/issues/221
[2] https://pypi.org/project/recommonmark/
[3] https://myst-parser.readthedocs.io/en/latest/
[4] https://doc.coreboot.org/getting_started/writing_documentation.html

Change-Id: I0837c1722fa56d25c9441ea218e943d8f3d9b804
Signed-off-by: Nicholas Chin <nic.c3.14@gmail.com>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/73158
Reviewed-by: Matt DeVillier <matt.devillier@gmail.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>

2 files changed, 10 insertions, 6 deletions

diff --git a/Documentation/soc/cavium/cn81xx/index.md b/Documentation/soc/cavium/cn81xx/index.md
index 684948cfd6..df6c44f4b1 100644
--- a/Documentation/soc/cavium/cn81xx/index.md
+++ b/Documentation/soc/cavium/cn81xx/index.md
@@ -2,7 +2,7 @@
 
 ## Reference code
 
-```eval_rst
+```{eval-rst}
 The Cavium reference code is called `BDK`_ (board development kit) and is part
 of the `Octeon-TX-SDK`_. Parts of the `BDK`_ have been integrated into coreoboot.
 ```
@@ -30,7 +30,7 @@ Cavium SoC do **not** have embedded SRAM. The **BOOTROM** setups the
 L2 cache and loads 192KiB of firmware starting from 0x20000 to a fixed
 location. It then jumps to the firmware.
 
-```eval_rst
+```{eval-rst}
 For more details have a look at `Cavium CN8XXX Bootflow`_.
 ```
 
@@ -46,7 +46,7 @@ aarch64 `bootblock.S` code.
 
 ## DRAM setup
 
-```eval_rst
+```{eval-rst}
 The DRAM setup is done by the `BDK`_.
 ```
 
@@ -112,7 +112,7 @@ memory reads as 0xffffffff.)
 Read the BDK_RNM_CTL_STATUS register at least once after writing it.
 
 
-```eval_rst
+```{eval-rst}
 .. _Octeon-TX-SDK: https://github.com/Cavium-Open-Source-Distributions/OCTEON-TX-SDK
 .. _Cavium CN8XXX Bootflow: ../bootflow.html
 .. _BDK: ../../../vendorcode/cavium/bdk.html
diff --git a/Documentation/soc/cavium/index.md b/Documentation/soc/cavium/index.md
index 5ccb47f611..ac94be593e 100644
--- a/Documentation/soc/cavium/index.md
+++ b/Documentation/soc/cavium/index.md
@@ -4,5 +4,9 @@ This section contains documentation about coreboot on specific Cavium SOCs.
 
 ## Platforms
 
-- [CN81xx series](cn81xx/index.md)
-- [CN8xxx bootflow](bootflow.md)
+```{toctree}
+:maxdepth: 1
+
+CN81xx series <cn81xx/index.md>
+CN8xxx bootflow <bootflow.md>
+```