Implement WooCommerce Redirect Modal Trigger Logic for Ads Module Setup via Settings

[10upsimon]

Feature Description

The WooCommerce redirect modal should be triggered as early as possible for users opting to setup ads and whom meet the criteria of the modal, hence the triggering of this banner from the Ads Module Setup CTA Banner as well, see #10175.

Another early capture point is the Settings > Connect More Services view, where the WooCommerce Redirect Modal should be triggered when said qualifying users click on the "Set up Ads" CTA, as per the below screenshot:

The modal should be triggered for users satisfying any of the following criteria:

The user has WooCommerce installed but not Google for WooCommerce

The user has both WooCommerce & Google for WooCommerce installed, but no Ads account linked via Google for WooCommerce

####The user has both WooCommerce & Google for WooCommerce installed, and has an Ads account linked via Google for WooCommerce

In all 3 of the above cases, the user should be given a choice to proceed with setting up Ads using Site Kit, via the secondary CTA of the modal. The primary CTA of each modal will be controlled by the modal component itself.

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• Users with WooCommerce installed, or WooCommerce & Google for Ads installed (regardless of an Ads account linked or not) should be presented with the WooCommerce redirect modal upon clicking the "Set up Ads" CTA in Settings > Connect More Services.
• Users choosing to proceed with Site Kit should be taken to the Ads setup flow as if they had never seen the modal.
• Users opting for the WooCommerce/Google for WooCommerce direction should be directed accordingly as per the logic in the modal, see Creation of <WooCommerceRedirectModal> Modal Component #10172 and Create New Ads Module Datastore Partial for Plugin Detection Selectors #10170 .

Implementation Brief

Test Coverage

QA Brief

Changelog entry

[10upsimon]

Triggering has also been outlined in #10172 so this issue is being closed out, cc @binnieshah