Clean up some remaining language about forging and pyscf (#481)

.github/workflows/test_latest_versions.yml

@@ -47,8 +47,4 @@ jobs:
           pver=${{ matrix.python-version }}
           tox -epy${pver/./} -- --run-slow
           notebook_flags=""
-          if [ "$RUNNER_OS" = "Windows" ]; then
-            echo Skipping tutorials \& how-tos that require pyscf
-            notebook_flags="${notebook_flags} --ignore=docs/_build/jupyter_execute/entanglement_forging/how-tos"
-          fi
           tox -epy${pver/./}-notebook -- ${notebook_flags}

INSTALL.rst

@@ -189,7 +189,3 @@ the toolbox within Docker <Option 3>`.  Other methods include:
     create a virtual environment that uses Python compiled for the x86
     instruction set.  No matter the installation method, there is a
     performance cost due to emulation.
-  - Advanced Windows users may wish to attempt to install PySCF using
-    the `Windows Subsystem for Linux
-    <https://learn.microsoft.com/en-us/windows/wsl/install>`__.  If
-    you have success using this method, please let us know.

README.md

@@ -36,8 +36,7 @@ Each tool in the CKT partitions a user's problem into quantum and classical comp
 The toolbox enables users to run parallelized and hybrid (quantum + classical) workloads without worrying about allocating and managing underlying infrastructure.
 
 The toolbox currently contains the following tools:
-- Entanglement Forging [[1]](#references)
-- Circuit Cutting [[2-7]](#references)
+- Circuit Cutting [[1-6]](#references)
 
 ----------------------------------------------------------------------------------------------------