Spike: Determine which WCS flows need E2E tests

We would like to get all important WCS flows under E2E tests this quarter so we have a strong foundation of tests to build on when we need to refactor and build new functionality.

The goal of this Spike is to check for flows that are not currently covered. We should also check for flows that affect site customers (e.g. automated taxes and live rates).

Note: it's not the same codebase, but while we're at it, we should also include the wc-admin onboarding prompt in this Spike.

Output:
- GitHub issues in WCS to create flows (with `[Type] E2E` )
- Include as much detail as possible so test writer covers important functionality
- GitHub issues to improve E2E test infrastructure (if needed)
- Master thread post on the wcship P2 summarizing results and linking all open GitHub issues