Ignore cached plugin data when checking if plugins are WooCommerce-aware

[barryhughes]

Submission Review Guidelines:

• I have followed the WooCommerce Contributing Guidelines and the WordPress Coding Standards.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have reviewed my code for security best practices.
• Following the above guidelines will result in quick merges and clear and detailed feedback when appropriate.

Changes proposed in this Pull Request:

If WooCommerce detects that one or more plugins are not compatible with an enabled feature, it tries to warn the merchant and provide a list of the relevant plugins. In some cases, though, the list may be empty (even if incompatible plugins are present):

This can happen if another plugin calls get_plugins() early in the request (before WooCommerce can filter it, and add WooCommerce header information to each plugin).

Closes #37343.

How to test the changes in this Pull Request:

Please install, but do not activate, the following plugins (the zip file contains two single-file plugins):

💾 Download Test Plugins

• Issue #37343 ▸ Plugin A (test plugin A) is the plugin that causes the problem, by making a very early call to get_plugins().
• Issue #37343 ▸ Plugin B (test plugin B) is a WooCommerce-aware plugin that declares incompatibility with HPOS.

Once you've set things up, proceed as follows:

1. Enable HPOS via WooCommerce ▸ Settings ▸ Advanced ▸ Features.
2. Visit the main plugin screen and activate test plugins A and B.
3. Return to (and refresh if needed) the feature admin page. You should find a link to manage incompatible plugins:

4. Follow the link, and you should be brought to a filtered version of the plugin list table. Without this change, the list will be empty. With this change, it should include at least test plugin B:

☝️ Note the presence of the inline notification, below plugin B, further calling attention to the fact that the incompatibility is with HPOS. This should also be present when the fix branch is applied.

[github-actions]

Hi @rrennick,

Apart from reviewing the code changes, please make sure to review the testing instructions as well.

You can follow this guide to find out what good testing instructions should look like:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

[barryhughes]

Temporarily removing the review request, there may be another aspect that needs to be addressed.

[github-actions]

Test Results Summary

Commit SHA: a473a00

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	1m 2s
E2E Tests	190	0	0	18	0	208	15m 21s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[barryhughes]

Back to review! Testing instructions updated.

[rrennick]

Nice work @barryhughes . Works as descibed.