Fix E2E gtag events for a blockified confirmation page.

[jorgemd24]

Changes proposed in this Pull Request:

Currently, there's a fatal error due to this issue: woocommerce/woocommerce-blocks#11851 and a "blockified" confirmation page. This problem is caused because the hook woocommerce_before_thankyou is being called with incorrect parameters.

Additionally, our E2E tests are failing. Check here: https://github.com/woocommerce/google-listings-and-ads/actions/runs/6942346039/job/18885109983?pr=2160. The blockified confirmation page uses a different class for the order status.

This PR introduces a temporary solution for the mentioned issue and resolves the E2E test problem.

Screenshots:

Detailed test instructions:

Fatal Error in the confirmation page. This has been fixed in WC 8.3.1 p1700588910958219-slack-C01DT6U03HC
1. Use WC 8.3
2. Use a theme that supports blocks, for example twenty twenty-two.
3. Blockify your confirmation page. See instructions here: https://woo.com/document/cart-checkout-blocks-status/ (Search for "Replacing the order confirmation page" )
4. Buy a product and complete the order, you shouldn't get any fatal error.
5. Checkout develop and repeat the steps and you will get a fatal error.

E2E Tests

1. Check that E2E are ✅ .

Additional details:

• I added await page.waitForTimeout( 3000 ); because it was clicking the button too quickly making the tests fail.

Changelog entry

Fix - E2E gtag evens tests.

[codecov]

Codecov Report

Merging #2161 (f3ea025) into release/2.5.12 (7264052) will decrease coverage by 0.0%.
Report is 2 commits behind head on release/2.5.12.
The diff coverage is 0.0%.

❗ Current head f3ea025 differs from pull request most recent head d28e604. Consider uploading reports for the commit d28e604 to get more accurate results

Additional details and impacted files

@@                Coverage Diff                 @@
##             release/2.5.12   #2161     +/-   ##
==================================================
- Coverage              58.3%   58.3%   -0.0%     
- Complexity             4119    4120      +1     
==================================================
  Files                   452     452             
  Lines                 17679   17681      +2     
==================================================
  Hits                  10305   10305             
- Misses                 7374    7376      +2     

Flag	Coverage Δ
php-unit-tests	58.3% <0.0%> (-<0.1%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
src/Google/GlobalSiteTag.php	0.0% <0.0%> (ø)

[eason9487]

Thanks for fixing the E2E tests. LGTM.

Left an alternative method to avoid clicking the button too quickly and it's not a blocker for this PR.

[eason9487]

I commented out this line and ran the related tests several times, and all attempts can pass.

• I added await page.waitForTimeout( 3000 ); because it was clicking the button too quickly making the tests fail.

Maybe an alternative method is to wait for the button to be enabled:

Suggested change

	//TODO: See if there's an alternative method to click the button without relying on waitForTimeout.
	await page.waitForTimeout( 3000 );
	await expect( page.locator( 'text=Place order' ) ).toBeEnabled();

[jorgemd24]

Thanks for the suggestion! Locally the E2E tests failed for me, even with the suggestion that you mentioned. For now, I will keep it as it is. If I find the root cause I will change it.