Enable users to seamlessly set up conversion tracking during the onboarding flow

[eason9487]

Changes proposed in this Pull Request:

Closes #2215

This PR wraps up all PRs related to #2215:

• [R-1] Enable users to seamlessly set up conversion tracking, without having to set up merchant center first or requiring campaign creation #2205
• [R-1.1] Update tests for conversion tracking without a merchant account #2223
• [R-1.1] Move useGoogleAccountCheck to its own file #2227
• [R-1.2] Update step 4 of the onboarding flow #2248
• [R-1.3] Add Google Ads invite acceptance flow #2270
• [R-1] Update E2E tests for setup flow with Ads setup in Step 1 #2308
• [R-1.3] Fix onboarding flow skipping to step 2 #2320
• Avoid a possible error when linking accounts due to the delay between Google APIs #2412
• Simplify and enhance the loading state control during the Google Ads account creation and claiming #2413
• Adjust event tracking for the creating and claim buttons of Google Ads account #2419
• Adjust click event tracking when connecting, disconnecting, and opening billing setup for Google Ads account #2421

📌 Checklist before merging

• Final round of overall testing
• Sync the latest develop branch and update tracking README file

Changelog entry

[codecov]

Codecov Report

Attention: Patch coverage is 76.24309% with 43 lines in your changes missing coverage. Please review.

Project coverage is 63.4%. Comparing base (6eb93ab) to head (340cb89).

Additional details and impacted files

@@             Coverage Diff              @@
##             develop   #2415      +/-   ##
============================================
- Coverage       64.2%   63.4%    -0.7%     
============================================
  Files            755     321     -434     
  Lines          21538    5027   -16511     
  Branches        1157    1218      +61     
============================================
- Hits           13818    3188   -10630     
+ Misses          7559    1672    -5887     
- Partials         161     167       +6     

Flag	Coverage Δ
js-unit-tests	63.4% <76.2%> (+0.6%)	⬆️
php-unit-tests	?

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

Files	Coverage Δ
js/src/components/account-card/index.js	96.8% <ø> (ø)
...ts/google-ads-account-card/claim-account-button.js	100.0% <100.0%> (ø)
...nts/google-ads-account-card/claim-account/index.js	100.0% <100.0%> (ø)
...nents/google-ads-account-card/connect-ads/index.js	96.0% <100.0%> (ø)
...-account-card/connected-google-ads-account-card.js	0.0% <ø> (ø)
...s/google-ads-account-card/create-account-button.js	11.1% <100.0%> (ø)
...omponents/google-ads-account-card/disabled-card.js	100.0% <100.0%> (ø)
...ents/google-ads-account-card/disconnect-account.js	100.0% <100.0%> (ø)
...nents/google-ads-account-card/terms-modal/index.js	100.0% <100.0%> (ø)
...onents/paid-ads/billing-card/billing-setup-card.js	92.9% <100.0%> (+63.4%)	⬆️
... and 18 more

... and 469 files with indirect coverage changes

[eason9487]

PHP Unit Tests failed because WooCommerce did backport fixes for versions 7.8.3-8.9.2, but these versions are listed in WordPress.org API but are still draft releases on GitHub.

It should be fine to continue the merge as the test passed in c5fe2d8 and the subsequent commits don't have any PHP changes.