Drop mentioning of JUMPSTARTER_CONFIG

Author: NickCao

docs/source/cli/run-tests.md

@@ -14,20 +14,12 @@ service.
 Alternatively the client can receive the endpoint and token as environment variables:
 
 ```bash
-export JUMPSTARTER_ENDPOINT=jumpstarter.my-lab.com:1443
-export JUMPSTARTER_TOKEN=dGhpc2lzYXRva2VuLTEyMzQxMjM0MTIzNEyMzQtc2Rxd3Jxd2VycXdlcnF3ZXJxd2VyLTEyMzQxMjM0MTIz
+export JMP_ENDPOINT=jumpstarter.my-lab.com:1443
+export JMP_TOKEN=dGhpc2lzYXRva2VuLTEyMzQxMjM0MTIzNEyMzQtc2Rxd3Jxd2VycXdlcnF3ZXJxd2VyLTEyMzQxMjM0MTIz
 ```
 
 This is useful for CI/CD systems that inject the environment variables into the pipeline.
 
-A custom location to the client configuration can also be passed using the following
-environment variable. This is useful in situations where there are multiple client
-configurations or in an environment when the config is mounted as a file.
-
-```bash
-export JUMPSTARTER_CONFIG=/etc/jumpstarter/my-client.yaml
-```
-
 ## Running tests locally (without a server)
 
 When no client configuration or environment variables are set, the client will