CI/Docs: remove the section regarding running the tests

And redirect to the CI instead.
The tests take too much time to run, and it is useless as it is tested in the CI.

Author: dannywillems

.github/workflows/test-docs-scripts.yml

@@ -58,12 +58,6 @@ jobs:
           source ~/.cargo/env
           ./website/docs/developers/scripts/setup/format-and-lint.sh
 
-      - name: Test run tests
-        run: |
-          # Source cargo environment first
-          source ~/.cargo/env
-          ./website/docs/developers/scripts/setup/run-tests.sh
-
       - name: Verify installations
         run: |
           echo "Verifying installed tools..."
@@ -120,12 +114,6 @@ jobs:
           source ~/.cargo/env
           ./website/docs/developers/scripts/setup/format-and-lint.sh
 
-      - name: Test run tests
-        run: |
-          # Source cargo environment first
-          source ~/.cargo/env
-          ./website/docs/developers/scripts/setup/run-tests.sh
-
       - name: Verify installations
         run: |
           echo "Verifying installed tools..."

website/docs/developers/getting-started.mdx

@@ -17,7 +17,6 @@ import InstallDockerMacOSSh from "!!raw-loader!./scripts/setup/install-docker-ma
 import InstallWasmToolsSh from "!!raw-loader!./scripts/setup/install-wasm-tools.sh";
 import CloneAndBuildSh from "!!raw-loader!./scripts/setup/clone-and-build.sh";
 import BuildSpecializedSh from "!!raw-loader!./scripts/setup/build-specialized.sh";
-import RunTestsSh from "!!raw-loader!./scripts/setup/run-tests.sh";
 import FormatAndLintSh from "!!raw-loader!./scripts/setup/format-and-lint.sh";
 
 Welcome to OpenMina development! This guide will help you set up your
@@ -116,7 +115,11 @@ components:
 
 ### 3. Run Tests
 
-<CodeBlock language="bash">{RunTestsSh}</CodeBlock>
+You can run a different set of tests. The command `make help` will give you the
+whole set of targets. You can also visit the file
+[ci.yaml](https://github.com/o1-labs/openmina/blob/develop/.github/workflows/ci.yaml)
+to explore the targets used for testing in our continuous integration
+environment.
 
 ## Development Workflow