Specify args for wp.data resolution in marketing page to support WP 5.9

[ecgan]

All Submissions:

• Have you followed the WooCommerce Contributing guideline?
• Does your code follow the WordPress' coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

Closes #37176.

In this PR, we specify empty array [] as the second argument for calls to invalidateResolution in marketing page to make it work with WordPress 5.9.

To make things consistent, we also specify empty array [] as the second argument for calls to hasFinishedResolution.

How to test the changes in this Pull Request:

• Have you followed the Writing high-quality testing instructions guide?

Functionality test:

Pre-conditions:

• Use WordPress 5.9.
• Enable WooCommerce Multichannel Marketing experience in WooCommerce Settings > Advanced > Features page: /wp-admin/admin.php?page=wc-settings&tab=advanced&section=features

1. Go to WooCommerce Marketing page: /wp-admin/admin.php?page=wc-admin&path=%2Fmarketing
2. Install and activate a channel that registers itself as a marketing channel, e.g. Google Listings and Ads.
3. You should see the channel appears as a registered channel in the Channels card (i.e. it should not disappear and be gone).

Code check

1. Search for invalidateResolution under the plugins/woocommerce-admin/client/marketing folder. Make sure all the calls to the function has the second argument specified.
2. Search for hasFinishedResolution under the plugins/woocommerce-admin/client/marketing folder. Make sure all the calls to the function has the second argument specified.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes, as applicable?
• Have you created a changelog file for each project being changed, ie pnpm --filter=<project> changelog add?
• Have you included testing instructions?

FOR PR REVIEWER ONLY:

• I have reviewed that everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities. I made sure Linting is not ignored or disabled.

[ecgan]

@eason9487 , here's the fix to the recent issue #37176 that you brought up in code review on my PR #37044. Could you review this please? 🙏

[github-actions]

Test Results Summary

Commit SHA: 580e3a8

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	1m 0s
E2E Tests	189	0	0	6	0	195	14m 0s

---

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.

[codecov]

Codecov Report

Merging #37198 (580e3a8) into trunk (0cf5677) will increase coverage by 0.0%.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff            @@
##             trunk   #37198   +/-   ##
========================================
  Coverage     46.7%    46.7%           
  Complexity   17191    17191           
========================================
  Files          429      429           
  Lines        64845    64845           
========================================
+ Hits         30275    30277    +2     
+ Misses       34570    34568    -2     

Impacted Files	Coverage Δ
...ugins/woocommerce/includes/class-wc-post-types.php	2.8% <ø> (ø)

... and 1 file with indirect coverage changes

[eason9487]

Thanks for the fix. LGTM.