If one onboards with WooPayments and then resets the onboarding to start over, the "shell" WooPayments gateways are still reported as enabled even if the "main" provider gateway is not. This is an inconsistency from the WooPayments client, but we need to handle it gracefully.

The issue stems from the fact that, when determining the additional data for the Payments task, we fetch the providers not for display purposes; this leads to including the shell gateways also. We need to investigate if it is safe to fetch the providers for display purposes or specifically filter out shell gateways in the Payments task logic.