chore: update PHP CI workflow

[marandaneto]

💡 Motivation and Context

Keep the PHP CI workflow aligned with project metadata changes, reduce wasted CI work, and separate regular test runs from coverage collection.

💚 How did you test it?

• composer validate --no-check-lock --no-check-version --strict

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog.

If releasing new changes

• Ran pnpm changeset to generate a changeset file

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
.github/workflows/php.yml:64-80
**Coverage runs even when tests fail**

The `coverage` job has no `needs: phpunit` dependency, so it will execute in parallel with (or regardless of) the `phpunit` matrix. If tests are failing, this wastes a runner slot and can produce misleading coverage output for a broken build. Adding `needs: [phpunit]` would keep coverage reporting gated on a green test run.

_{Reviews (1): Last reviewed commit: "chore: update PHP CI workflow" | Re-trigger Greptile}

[greptile-apps]

_{Reviews (2): Last reviewed commit: "chore: address PHP CI feedback" | Re-trigger Greptile}

[dustinbyrne]

codeql warnings are worth addressing

[marandaneto]

codeql warnings are worth addressing

Which ones? I dont see any as comments