Print test names as MySQL step enters each test for CI hang diagnosis

Same diagnostic approach 8295e60 applied to the Postgres step. The MySQL
suite just hit a Mode-B hang (CI run 24637564241) around tests 882-913
with no loud error — only the progress-dot batch, then silence until the
60m step budget. --testdox alone prints test names on completion, so the
hang is invisible in the step log. --debug prints each test name as it
enters, so the next red run names the hang point.

Drop alongside the Postgres --debug when #427 closes and MySQL has been
consistently green for a cycle.

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

Author: durable-workflow-ops

.github/workflows/php.yml

@@ -76,10 +76,16 @@ jobs:
         touch testbench.sqlite
         mysql -e 'CREATE DATABASE testbench' -h127.0.0.1 -uroot -ppassword -P ${{ job.services.mysql.ports[3306] }}
 
+    # --debug prints each test name as it starts so when the suite stalls
+    # the hang point is visible in the step log instead of hidden behind
+    # the 60m timeout. Currently chasing a stall around tests 882-913 that
+    # only reproduces in CI (runs 24635883692 and 24637564241). Drop --debug
+    # when the cluster tracked under #427 / the post-#429 MySQL flake is
+    # resolved and MySQL has been consistently green.
     - name: Run test suite (MySQL)
       id: mysql_suite
       timeout-minutes: 65
-      run: timeout --foreground 60m vendor/bin/phpunit --testdox --testsuite feature
+      run: timeout --foreground 60m vendor/bin/phpunit --testdox --debug --testsuite feature
       env:
         DB_CONNECTION: mysql
         DB_PORT: ${{ job.services.mysql.ports[3306] }}