Tooling: Run Phan against Woo versions

[tbradsha]

Closes MONOREP-232

This PR runs Phan against older Woo stubs. I've put the new test in the linting workflow (now that said workflow runs on trunk as well).

Proposed changes:

We've had a few cases where Jetpack releases have unleashed some fatals because an assumption that users ran fairly recent WooCommerce versions.

p1759248959778399/1759158780.923629-slack-CK365S85V
p1763478353571209/1763474992.105219-slack-CK365S85V
p1759758846239149/1759158780.923629-slack-CK365S85V

If there's a need we could consider generating new woocommerce-internal stubs, but that'd be for another PR should we want.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

Hopefully there's a new "Static analysis (WooCommerce)" job in the CI that completes successfully.

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[anomiex]

We could merge this into the existing Phan run as a three line change: two adding the WOO_VERSION constant with a comment and one adding "php-stubs/woocommerce-stubs:${WOO_VERSION}" to the existing composer update command.

Is there a benefit to doing this as a completely separate run?

[anomiex]

Ok, four lines: one more to mention old-Woo in the name of the step too.

[tbradsha]

Initially I had it configured to run on 4 Woo versions, so a separate job made sense.

Now it's only running on one Woo version, and it'd be a simple change to move it into the current Phan run, but that already takes 10 minutes. Adding the old Woo run to the existing one would extend that another 5 minutes (wall time), which is a painful amount of time to wait for something to pass or fail.

[anomiex]

Adding the old Woo run to the existing one would extend that another 5 minutes (wall time)

That's not what I suggested. Still two runs, just the second would be "old WP and old Woo" instead of only "old WP" (and this separate one for "old Woo").

[tbradsha]

Misread. Sounds like a plan!

[tbradsha]

I'll close this in favor of a new one after #46026 is merged.