sphinx version 6.0.0 is not compatible with myst-parser

[arkodg]

Description:
Bumping sphinx to 6.0.0 from 5.3.0 using #841 broke docs on the main branch, since a dependent package (myst-parser) is not compatible with this version yet

make docs
===========> Running docs.clean ... 
rm -rf docs/html
mkdir -p tools/bin/sphinx-build.d
python3 -m venv tools/bin/sphinx-build.d/venv
tools/bin/sphinx-build.d/venv/bin/pip3 install -r tools/src/sphinx-build/requirements.txt || (rm -rf tools/bin/sphinx-build.d/venv; exit 1)
Collecting Sphinx==6.0.0
  Downloading sphinx-6.0.0-py3-none-any.whl (3.0 MB)
     |████████████████████████████████| 3.0 MB 4.9 MB/s 
Requirement already satisfied: myst-parser==0.18.1 in ./tools/bin/sphinx-build.d/venv/lib/python3.9/site-packages (from -r tools/src/sphinx-build/requirements.txt (line 2)) (0.18.1)
Requirement already satisfied: pyyaml in ./tools/bin/sphinx-build.d/venv/lib/python3.9/site-packages (from myst-parser==0.18.1->-r tools/src/sphinx-build/requirements.txt (line 2)) (6.0)
Requirement already satisfied: markdown-it-py<3.0.0,>=1.0.0 in ./tools/bin/sphinx-build.d/venv/lib/python3.9/site-packages (from myst-parser==0.18.1->-r tools/src/sphinx-build/requirements.txt (line 2)) (2.1.0)
Requirement already satisfied: jinja2 in ./tools/bin/sphinx-build.d/venv/lib/python3.9/site-packages (from myst-parser==0.18.1->-r tools/src/sphinx-build/requirements.txt (line 2)) (3.1.2)
ERROR: Cannot install Sphinx==6.0.0 and myst-parser==0.18.1 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested Sphinx==6.0.0
    myst-parser 0.18.1 depends on sphinx<6 and >=4

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Repro steps:
make docs

[danehans]

@arkodg do you know if dependabot will create another PR to bump this dep? If so, we should keep this issue open and configure it to unmanage sphinx until myst-parser is compatible with 6.0.0.

[arkodg]

@danehans #849 handles this by unmanaging it and adding a note to re-enable it once issue is fixed

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days.