feat: segmentation criteria for subscriptions and memberships

[dkoo]

All Submissions:

• Have you followed the Newspack Contributing guideline?
• Does your code follow the WordPress' coding standards and VIP Go 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:

Along with Automattic/newspack-popups#1230, adds support and UI for two new sets of criteria, based on subscriptions and memberships.

Also splits the UI for the single segment screen into smaller subsections, as the current set of sections was looking crowded as we add more criteria. (cc @thomasguillot)

Note that I moved some files around and renamed some others for consistency.

• The ListsControl component is only used in the context of the Campaigns wizard, so I moved it out of the Newspack Components directory and into the components for the wizard. Also made this more abstract so it could be reused for all of the list__in and list__not_in criteria.
• Renamed some of the components files in the Campaigns wizard folder from CamelCase to kebab-case, which matches most of our file naming across repos. Didn't try to be exhaustive about this.
• Made some minor style and markup updates to the AutocompleteTokenfield component, to make the placement of the spinner component during loading more consistent and predictable.

Closes 1205451924709229/1205603536115944.

How to test the changes in this Pull Request:

1. On master, register two new user accounts in separate sessions. On Account A, purchase a non-donation subscription product. On Account B, join any membership plan by satisfying the plan's requirements for granting access.
2. Check out this branch and feat: segmentation criteria for subscriptions and memberships newspack-popups#1230. Create two new segments at the highest priority, one for Subscriptions with "Has active subscription(s)" targeting the subscription product purchased by Account A, and one for Memberships with "Has active membership(s)" targeting the membership plan joined by Account B. Also note the new organization of the single segment screen here, which splits the "Reader Activity" section into three separate sections:

3. Test support for segmenting user accounts who already have active subscriptions/memberships upon login. In separate sessions, log in as Account A and Account B and confirm that after logging in, each session gets segmented to the corresponding subscription/membership segment.
4. Test support for new subscriptions/memberships: In two new sessions, purchase the required subscription product and join the required membership plan. In each case confirm that you're segmented after completing the purchase/membership action.
5. Test support for changes subscription/membership statuses. As an admin, cancel the subscription/membership for the test users. Log in as those test users and confirm that you no longer match the segments.
6. Also test the new "Does not have active subscription/membership" criteria: the test users who have active subscriptions and memberships matching these criteria should not match these segments, while everyone else should.

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 successfully ran tests with your changes locally?

[adekbadek]

Left some non-blocking comments.

[dkoo]

Also in 6b26f57, I fixed (hopefully for the last time) a style error in the positioning of the loading spinner for the AutocompleteTokenfield component. It should now always be overlaid on the autocomplete input field, whether or not there's a label or help description, and whether or not suggestions are being displayed.

[matticbot]

🎉 This PR is included in version 2.11.0-alpha.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 2.11.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀