Add the governance plugin

[ingeniumed]

Description

This is meant to add the VIP governance plugin as an integration in mu-plugins, alongside the Block Data API. It's using the existing VIP integrations framework that's already in place for the Block Data API and Parsely to do this.

I have also added 2 test for the Block Data API and the VIP Governance plugin that simply tries to load them, and then verifies if they are inactive. It also calls their is_loaded function which checks if their constant is defined which should be false. Unlike the parsely plugin, their code isn't there so the code that can be tested is limited unfortunately.

The corresponding PR in mu-plugins-ext has been made here. That should be merged first.

Changelog Description

Plugin Added: VIP Governance 1.0

We added VIP Governance Plugin 1.0 for VIP customers.

This is a plugin that adds additional governance capabilities to the block editor.

Pre-review checklist

Please make sure the items below have been covered before requesting a review:

• This change works and has been tested locally (or has an appropriate fallback).
• This change works and has been tested on a Go sandbox.
• This change has relevant unit tests (if applicable).
• This change uses a rollout method to ease with deployment (if applicable - especially for large scale actions that require writes).
• This change has relevant documentation additions / updates (if applicable).
• I've created a changelog description that aligns with the provided examples.

Pre-deploy checklist

• VIP staff: Ensure any alerts added/updated conform to internal standards (see internal documentation).

Steps to Test

Example:

1. Check out PR, along with this PR as well.
2. Use this as your mu-plugins in a local dev-env instance
3. Activate using the following:

// client-mu-plugins/plugin-loader.php

\Automattic\VIP\Integrations\activate( 'vip-governance' );

4. Go to wp-admin > Plugin and ensure VIP Governance shows up
5. Go to wp-admin > VIP Governance and ensure that loads correctly
6. Go to the a new post page and ensure everything loads fine.

[codecov]

Codecov Report

Merging #4907 (f9cf630) into develop (8de9938) will increase coverage by 0.02%.
Report is 2 commits behind head on develop.
The diff coverage is 35.71%.

@@              Coverage Diff              @@
##             develop    #4907      +/-   ##
=============================================
+ Coverage      29.20%   29.23%   +0.02%     
- Complexity      4726     4730       +4     
=============================================
  Files            277      278       +1     
  Lines          20830    20844      +14     
=============================================
+ Hits            6083     6093      +10     
- Misses         14747    14751       +4     

Files	Coverage Δ
vip-integrations.php	38.09% <0.00%> (-6.35%)	⬇️
integrations/vip-governance.php	45.45% <45.45%> (ø)

... and 3 files with indirect coverage changes

[ingeniumed]

I ended up adding this here as this is where the registrations happen for the actual plugins. The underlying logic with the real plugins is better tested with the fake-integration that's in the unit tests. Instead, I added two tests for two of the integrations that didn't have unit tests and attempted to add what I could in there.

So for next time if an integration is added, what would be done is:

• Add the integration here
• Add the integration under integrations, and then add a test for it as well.

So that way as much of the new code is covered via the unit test.

Hope that makes sense, and makes it clear why I did this.

[mehmoodak]

It seems like the function name is not matching with assert statement.