Github PHP changes workflow: remove it

[ramonjd]

Removing the PHP changes workflow

Why?

The PHP detections action checks for PHP changes and adds a comment to ask whether a backport is necessary.

Example:

I think it's just noise now that the check backport changelog workflow is in place.

Also to reduce clutter.

[noisysocks]

Looks good to me unless anyone in @WordPress/gutenberg-core has any objections 👍

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: tellthemachines <isabel_brison@git.wordpress.org>
Co-authored-by: noisysocks <noisysocks@git.wordpress.org>
Co-authored-by: ellatrix <ellatrix@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[tellthemachines]

This makes sense, thanks for the cleanup!

[ellatrix]

No objections, if you think the failing test is enough. I was wondering if the backport log test should leave an actual Github comment instead, though there should be a clear error message if you open the test results.

[github-actions]

Flaky tests detected in c5bd1de.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9543945900
📝 Reported issues:

• [Flaky Test] Redirection after template creation #60678 in /test/e2e/specs/site-editor/site-editor-url-navigation.spec.js