Move external tests files to tests/external/

docs/ARCHITECTURE.md

@@ -56,8 +56,10 @@ rgbds/
 │   ├── bison.sh
 │   └── ...
 ├── test/
-│   ├── fetch-test-deps.sh
 │   ├── run-tests.sh
+│   ├── external/
+│   │   ├── fetch-repos.sh
+│   │   └── ...
 │   └── ...
 ├── .clang-format
 ├── .clang-tidy
@@ -110,10 +112,15 @@ rgbds/
     Script used to run the Bison parser generator with the latest flags that the user's version supports.
 - **`test/`:**  
   Testing framework used to verify that changes to the code don't break or modify the behavior of RGBDS.
-  * **`fetch-test-deps.sh`:**  
-    Script used to fetch dependencies for building external repositories. `fetch-test-deps.sh --help` describes its options.
+  The `test.sh` scripts inside each of the subdirectories are the individual test drivers.
   * **`run-tests.sh`:**  
     Script used to run tests, including internal test cases and external repositories. `run-tests.sh --help` describes its options.
+  * **`external/`:**  
+    Directory for third-party repos making use of RGBDS, which get cloned here and built during testing.
+    - **`fetch-repos.sh`:**  
+      Script used to clone the external repositories. `fetch-repos.sh --help` describes its options.
+    - **`*.cfg`:**  
+      Each `.cfg` file defines the parameters to clone, build, and verify an external repository.
 - **`.clang-format`:**  
   Code style for automated C++ formatting with [`clang-format`](https://clang.llvm.org/docs/ClangFormat.html) (for which we define the shortcut `make format`).
 - **`.clang-tidy`:**  

docs/CONTRIBUTING.md

@@ -69,7 +69,7 @@ years). If you are adding new files, you need to use the
    You can also use `cmake --preset develop` if you prefer.
 5. Test your changes by running `./run-tests.sh` in the `test` directory.
    `./run-tests.sh --help` will print its available options. (You must run
-   `./fetch-test-deps.sh` first; if you forget to, the test suite will fail and
+   `external/fetch-repos.sh` first; if you forget to, the test suite will fail and
    remind you mid-way.)
    
    You can also use `ctest --test-dir build` if you prefer.

docs/RELEASE.md

@@ -10,7 +10,7 @@ GitHub.
      `PACKAGE_VERSION_MINOR`, `PACKAGE_VERSION_PATCH`, and `PACKAGE_VERSION_RC`.
      **Only** define `PACKAGE_VERSION_RC` if you are publishing a release candidate!
    - [Dockerfile](Dockerfile): update `ARG version`.
-   - [test/fetch-test-deps.sh](test/fetch-test-deps.sh): update test dependency commits
+   - [test/external/*.cfg](test/external): update test dependency commits
      (preferably, use the latest available).
    - [man/\*](man/): update dates and authors.