Add dashboard wincher connect patch

[pls78]

Context

• We want to show the Wincher section in the WordPress dashboard also when a user is not connected to their Wincher account.

Summary

This PR can be summarized in the following changelog entry:

• Shows a widget in the WordPress dashboard with a connection button in case a user has not connected to their Wincher account.
• Renders Wincher-related information in a separate dashboard widget.

Relevant technical choices:

• N/A

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:
Preliminary steps

• Make sure you have the Wincher integration active in Yoast SEO -> Integrations
• If you are connected to your Wincher account disconnect from it (e.g. by turning off and on again the Wincher integration card)
• If you're already tracking keywords please remove them

Test the new widget

• Go to Dashboard
• verify there's a widget like the one below:
  
• verify the link in Connect with Wincher to get started has the following format (parameters values may vary): https://yoa.st/dashboard-about-wincher?php_version=7.4&platform=wordpress&platform_version=6.2&software=premium&software_version=20.8-RC1&days_active=28&user_language=en_US
• verify the Get more insights over at Wincher link is the following: https://app.wincher.com/login?utm_medium=plugin&utm_source=yoast&referer=yoast&partner=yoast

Test connection error

• Click on the Connect blue button and connect to your Wincher account: a popup will appear
• Click to focus on the main window where your website is loaded
• Simulate being offline through your browser's developers tools
  • For Chrome
    • open the developers tools and go to the Network tab
    • click on No throttling and change it to offline
  • For Firefox

    • open the developers tools and go to the Network tab

    • click on the Request blocking icon
      

    • click on Enable Request Blocking

    • in the text field below add your base url (e.g. wordpress.test)

  • Go back to the login popup and complete the procedure
  • Go back to the browser console open in your main window and verify no Uncaught error is displayed
  • Click on the Connect button again and verify

    • the following alert appears

      

    • no Uncaught error is displayed in the browser's console

Test the widget's correct functioning

• Restore your connection and connect with Wincher; the following alert should appear:

  

• Add a focus keyphrase to some of your posts and track it with Wincher

  • In the metabox, verify the two links in With Wincher you can track the ranking position of your page in the search results based on your keyphrase(s). Read more about keyphrase tracking with Wincher have the following format:
    • https://yoa.st/wincher-popup?php_version=7.4&platform=wordpress&platform_version=6.2&software=premium&software_version=20.8-RC1&days_active=28&user_language=en_US
    • https://yoa.st/wincher-integration?php_version=7.4&platform=wordpress&platform_version=6.2&software=premium&software_version=20.8-RC1&days_active=28&user_language=en_US

• Go to Dashboard and verify your keywords appear in the Yoast SEO / Wincher: Top Keyphrases widget

• Add some more keyphrases and track them in order to reack your keyphrase quota (it's 5 for the free tier)

• Try to track another keyphrase and verify the Upgrade your Wincher plan link has the following format:

  • https://yoa.st/wincher-popup-pricing?php_version=7.4&platform=wordpress&platform_version=6.2&software=premium&software_version=20.8-RC1&days_active=28&user_language=en_US

Testing backward compatibility

• Install an older version of Yoast SEO
• Add some keyphrases to your posts and track them with Wincher
• Upgrade Yoast SEO to the version containing this PR
• Verify you can still see your keyphrases in the Yoast SEO / Wincher: Top Keyphrases

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Block/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

• N/A

UI changes

• This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

• I have written documentation for this change.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins Yoast SEO provides integrations for.
• I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label and noted the work hours.

Fixes #

[vraja-pro]

Suggested change

	isBlurred: PropTypes.object,
	isBlurred: PropTypes.bool,

[vraja-pro]

Suggested change

	children: PropTypes.object,
	children: PropTypes.oneOfType([
	PropTypes.string,
	PropTypes.number,
	PropTypes.object
	]),

[vraja-pro]

On dashboard when there is connection, I'm getting more errors in the console

[vraja-pro]

CR & AC ✅