Add check if plugin setup is completed

[samiuelson]

This PR updates conditions to show the POS entry point - now it's required that Woo Payments onboarding is complete.
Context: p91TBi-beb-p2#comment-12134

Testing instructions

• Verify "Woo POS" button is visible in the menu more screen if the Woo Payments onboarding is completed (plus other conditions are met – big screen size, USD currency, US location, and Woo Payments plugin activated)
• You can also verify the button is not present in case onboarding is not completed

• I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce Android
	Flavor	Jalapeno
	Build Type	Debug
	Commit	bab839e
	Direct Download	woocommerce-prototype-build-pr11549-bab839e.apk

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 40.44%. Comparing base (2b56352) to head (bab839e).
Report is 303 commits behind head on trunk.

Additional details and impacted files

@@            Coverage Diff            @@
##              trunk   #11549   +/-   ##
=========================================
  Coverage     40.44%   40.44%           
- Complexity     5196     5200    +4     
=========================================
  Files          1083     1083           
  Lines         62996    62999    +3     
  Branches       8628     8630    +2     
=========================================
+ Hits          25479    25482    +3     
  Misses        35224    35224           
  Partials       2293     2293           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[malinajirka]

⚠️ I'll follow up on the P2, but just a heads-up that this doesn't handle the scenario when there are pending but skippable requirements on the Stripe's account.

[samiuelson]

As per the decision (p91TBi-bje-p2), I've loosened the status requirement to ENABLED. I don't have a full understanding of all the status types though, so I'd appreciate it if you could confirm (@malinajirka or @kidinov) if the condition matches the following requirement:

- ...
- Onboarding is Completed (optional requirements should be considered as valid).
- ...

[kidinov]

@malinajirka @samiuelson 👋

As for M1, it's planned to implement a "happy path" only, shall we assume that only the completed state is exacted for now? Handling optional requirements is done on å full-screen fragments, so it may bring some complexity to the initial implementation of connection/payment flows. In any case I added a ticket to handle that - we just need to decide priorities - for M1 or latter.

#11612

[malinajirka]

Allowing users to enter the POS with pending requirements but crashing (implementing only the happy path) sounds like a good approach for now. I've added high priority label to the issue just to make sure we don't leave the code in the crashing state.

I've loosened the status requirement to ENABLED. I don't have a full understanding of all the status types though,

I believe this should be enough - we'll need to eventually test all the flows though. We had a pretty detailed test plan for the onboarding project so we should be able to look it up and re-use it.

[samiuelson]

I'm marking PR as a draft to wait for the final decision.

[malinajirka]

LGTM, thanks!