Conditionally load shipping functionality based on if WC Shipping is active

[kallehauge]

Description

Just playing around in context of paJDVv-3NH-p2

Fixes: 2766

We need to:

• [x] Update name of status page to (conditionally?) say "WooCommerce Tax" or "WooCommerce Tax & Shipping".
  • TL;DR: We shouldn't: https://github.com/Automattic/woocommerce-services/pull/2761/commits/d6fbe3e5141f5c28f6e2b984326ab0e0172962d5
• [x] The status page should also, conditionally, display shipping settings and content.
  • https://github.com/Automattic/woocommerce-services/pull/2776
• [x] We need to rename the tab from "connect" in WC Shipping since that's conflicting
  • https://github.com/woocommerce/woocommerce-shipping/pull/578
• [ ] We need to update our connect / ToS banners.
• [x] Verify that mobile will continue to work
  • The REST endpoints continue to be functional.
• [x] Since we expect WCS&T to be around for a while: maybe add a banner / notification saying WCS&T doesn't show WC Shipping labels if the merchant disabled the plugin afterwards (and that we do not support backwards migration)
  • The migration project already has enough "WC Shipping is activated" type communication.

What's working without issue:

• WPCOM connection!
• I'm able to fetch taxes without UI or debug.log warnings/errors
• I'm able to purchase shipping labels when using WC Shipping in parallel

Testing instructions

WCS&T

The first test is to ensure that WCS&T is functioning as it should on its own, things to test:

• Establishing a connection
• All label functionality
• Automated taxes
• Settings
• Debug info

WC Shipping combined with WCS&T

The second test would be to see how well WC Shipping works with WCS&T installed already. There are a couple of starting scenarios to test ie: establishing a connection with WCS&T and then activating WC Shipping and ensuring the connection is kept established, this is the most likely scenario that would be used in the wild, but we should also test for instances where WC Shipping is installed first and then you install WCS&T, does it allow for establishing a new connection for tax purposes in WCS&T.

Things to test include:

• Connections, WC Shipping and WCS&T have separate connections/tos agreements.
• Automated taxes, does it continue functioning
• Label functionality, does it utilise the label purchase flow from WC Shipping instead of WCS&T.
• WC Shipping settings, does the settings of WC Shipping show and work instead of that of WCS&T.
• Debugging info, are there no conflicts between the debug info from WCS&T and WC Shipping

Please test around this these instruction in any way you can think.

Related issue(s)

Steps to reproduce & screenshots/GIFs

Checklist

• [ ] unit tests

• [ ] changelog.txt entry added
• [ ] readme.txt entry added

[samnajian]

I then purchased new labels using WooCommerce Shipping and disabled WooCommerce Shipping to check what WooCommerce Shipping & Tax does, and for that order, it just shows the create shipping label button.

That's how it should work as we don't have data migration from WC Shipping to WCS&T.