feat(everlit): added Everlit to plugins + refactor plugins in connections wizard

[jaredrethman]

All Submissions:

• [x] Have you followed the Newspack Contributing guideline?
• [x] Does your code follow the WordPress' coding standards and VIP Go coding standards?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

Everlit plugin management. Due to the nature of the UX implementation of this feature it was necessary to do a rewrite of some of the logic within the <Plugins /> component used within Connections Wizard, namely:

• Ability to activate plugin when inactive and reload browser when activated.
• Different status, per/plugin, functionality.
• HTML within <ActionCard /> descriptions i.e. <a>Learn more</a>.
• Plugin Manager configuration for Everlit
• Configuration Manager Class for Everlit to request setup status.
• Abstracted individual Plugins into a separate component <Plugin /> to avoid re-renders on all ActionCards when a single plugins state changes.
• Loading indicators during requests.

How to test the changes in this Pull Request:

1. Checkout this branch and build assets i.e. git checkout origin/feat/wizard-everlit-plugin && npm run build
2. Navigate to /wp-admin/admin.php?page=newspack-connections-wizard
3. Observer the new ActionCard for Everlit is present.

4. Click "Install Everlit", once request has completed observe you see the following:

5. Click "Activate Everlit". Observe:
   • Once request has completed, page will reload (Necessary for Everlit Plugin settings to show once activated)
   • "Everlit" admin menu item exists after reload.
   • The Everlit plugin action card should resemble the below - prompting further setup.

6. Right click "Complete Setup" and open in a new tab, this will open a tab with Everlit initial setup. Add your details and click "Submit".

7. Navigate back to Connections tab and refresh page. Observe that further setup is still necessary.

8. Navigate back to Everlit settings tab and refresh page. Observe that different configuration is now available e.g. "Everlit Token". Add a "Everlit Token" (for testing purposes this can be anything) and click "Save Changes"
9. Navigate back to Connections tab and refresh. You should now see a successfully configured Everlit plugin.

Other information:

• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [ ] Have you written new tests for your changes, as applicable?
• [x] Have you successfully ran tests with your changes locally?

[kmwilkerson]

Nice! We can remove the Install step (as it'll be installed by default) and just start right with the activation step

[jaredrethman]

Nice! We can remove the Install step (as it'll be installed by default) and just start right with the activation step

@kmwilkerson I can absolutely remove it. Here's some motivations for keeping it:

• If the plugin is already "installed by default" user will never see the prompt to install.
• If there is ever a situation where the plugin wasn't able to be installed by default (network issues etc) the below wouldn't be accurate.
• Make testing this review that much easier.

Let me know your thoughts on the above.

[kmwilkerson]

I gotcha -- in that case, keeping it makes total sense @jaredrethman

[matticbot]

:tada: This PR is included in version 4.4.0-alpha.3 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

[matticbot]

:tada: This PR is included in version 4.4.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: