doc: Include documentation for test targeting via PYTEST_TESTS.

Also update the table of optional environment variables to set when
running the integration tests.

Author: s373nZ

doc/contribute-to-core-lightning/testing.md

@@ -41,11 +41,11 @@ There are four kinds of tests:
 
   `PYTHONPATH=contrib/pyln-client:contrib/pyln-testing:contrib/pyln-proto:contrib/pyln-grpc-proto py.test -v tests/`
 
-  Or alternatively, via the `Makefile`, by setting `PYTEST_TESTS`:
+  You can also append `-k TESTNAME` to run a single test.  Environment variables `DEBUG_SUBD=<subdaemon>` and `TIMEOUT=<seconds>` can be useful for debugging subdaemons on individual tests, and `DEBUG_LIGHTNINGD` for attaching a debugger to each `lightningd` instance created.
 
-  `PYTEST_TESTS="tests/test_askrene.py::test_layers" make pytest`
+  Or alternatively, run a single test via the `Makefile`, by setting `PYTEST_TESTS`:
 
-  You can also append `-k TESTNAME` to run a single test.  Environment variables `DEBUG_SUBD=<subdaemon>` and `TIMEOUT=<seconds>` can be useful for debugging subdaemons on individual tests, and `DEBUG_LIGHTNINGD` for attaching a debugger to each `lightningd` instance created.
+  `PYTEST_TESTS="tests/test_askrene.py::test_layers" make pytest`
 
 - **pylightning tests** - will check contrib pylightning for codestyle and run the tests in `contrib/pylightning/tests` afterwards: