test: Remove the system-test runner and its Python mock server

Every sample's system test now lives in the module it tests, so the
Python runner, its mock Sentry server, requirements.txt and the Makefile
targets that ran them have nothing left to run.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Author: runningcode

Makefile

@@ -1,4 +1,4 @@
-.PHONY: all clean compile javadocs dryRelease update checkFormat api assembleUiTestRelease assembleUiTestCriticalRelease runUiTestCritical setupPython systemTest systemTestInteractive check preMerge publish
+.PHONY: all clean compile javadocs dryRelease update checkFormat api assembleUiTestRelease assembleUiTestCriticalRelease runUiTestCritical check preMerge publish
 
 all: stop clean javadocs compile
 assembleUiTests: assembleUiTestRelease
@@ -46,20 +46,6 @@ assembleUiTestCriticalRelease:
 runUiTestCritical:
 	./scripts/test-ui-critical.sh
 
-# Create the Python virtual environment for system tests, and install the necessary dependencies
-setupPython:
-	@test -d .venv || python3 -m venv .venv
-	.venv/bin/pip install --upgrade pip
-	.venv/bin/pip install -r requirements.txt
-
-# Run system tests for sample applications
-systemTest: setupPython
-	.venv/bin/python test/system-test-runner.py test --all
-
-# Run system tests with interactive module selection
-systemTestInteractive: setupPython
-	.venv/bin/python test/system-test-runner.py test --interactive
-
 # Run tests and lint
 check:
 	./gradlew check