Review PHP tests on trunk branch

[juanfra]

PHP tests are running on trunk but all development happens in develop. This creates failing tests that are not actually related to any error and they're adding noise from testing an inactive branch.

I propose we disable PHP testing on trunk until we're actually doing work there. Keep tests running on develop where the real changes are happening. We can turn them back on when trunk becomes active.

[dkotter]

I understand the reasoning here but generally we like to run tests on trunk in order to catch issues as soon as possible. For instance, our tests on trunk are failing right now due to conflicts with our plugin loading the AI Client and the now bundled AI Client with WordPress. This is an issue we need to resolve so having these tests fail help flag that for us.

[juanfra]

Thanks for the context, that's helpful!

What if we set up a scheduled action to run the trunk tests nightly instead? We'd still catch issues like the AI Client conflict, just without the noise of 6 failed tests on every PR. Failed results could go to admins or get posted somewhere when things break.