Feat/network pass

[leogermani]

Creates the Network pass feature.

Also, this work surfaced a small issue with the plugin. The post_process_in_hub method was being called even for events that were triggered in the Hub itself. This would cause the local memberhips to get the post meta and they would become uneditable.

To be consistent, this method should not be called in such cases. Just as process_in_node is not called in node for their own events.

I slightly changed the architecture there and updated the docs. It should be good now.

** Testing

Setup

• On site A, create two membership plans
• In one of the plans, add any value to the new "Network ID" field

• Leave Network ID blank for the other membership plan
• Do the same on Site B, two memberships
• In one of the memberships, put the same Network ID

Now let's test the flow

• Create a new membership for a user in one of the sites - in the memberhips with a Network ID
• Confirm that a newspack_network_woo_membership_updated is triggered and added to the event log
• Once this event reaches the other site, confirm the user is created and a membership is granted to them in the membership plan that shares the same network id
• In the site where the membership was distributed to, confirm the link to edit the membership points to the original site, where the membership was first created
• Confirm the action links (when you hover the memberhip in the admin table) shows a message "Managed in {link}" with a link to the original membership

• Edit the orginal membership and change its status and confirm all status changes are properly propagated across the network
• Create a membership in the membership plan without a Network ID and confirm no events are triggered

[leogermani]

Thanks @adekbadek ,

I have fixed the link and changed the approach to block edition. I have now a check for the edit_post capability check. See what you think.

Also, this work surfaced a small issue with the plugin. The post_process_in_hub method was being called even for events that were triggered in the Hub itself. This would cause the local memberhips to get the post meta and they would become uneditable.

To be consistent, this method should not be called in such cases. Just as process_in_node is not called in node for their own events.

I slightly changed the architecture there and updated the docs. It should be good now.

(btw, I'm open to revisiting the method names)

[adekbadek]

Pre-approving, pending some wording suggestions.

[leogermani]

@adekbadek this is good to land. But leaving this un-merged to see how we want to proceed with the release, If we want to have this in an epic branch, a feature flag... or if it's fine since it will have no effect until a Network ID is set

[adekbadek]

I think we're good to go, just remember to add public-facing docs after the release.

[matticbot]

🎉 This PR is included in version 1.3.0-alpha.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[matticbot]

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀