Show RRM buttons on the edit post page for non-Site Kit users

[techanvil]

Feature Description

At present, when RRM blocks are included in a post, and a non-admin user who hasn't had any Site Kit modules shared with them edits the post, the blocks aren't registered and the following warnings are shown instead.

In this scenario, we should ensure the blocks are registered and the buttons display in the disabled state with an appropriate warning notice in the block sidebar.

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• When RRM blocks are included in a post, and a non-admin user who hasn't had any Site Kit modules shared with them (a "non-Site Kit user") edits the post:
  • The RRM buttons should be displayed in the disabled state.
  • An undismissible warning should be displayed in the block sidebar with this copy:
    • This block can only be configured by Site Kit users. Please contact your administrator.
  • The warnings about the blocks being unsupported should not be displayed.
  • No Site Kit data that's not directly needed for this functionality should be exposed to the non-Site Kit user.

Implementation Brief

• Add two new gutenberg block assets for non-Site Kit user versions of the RRM blocks.
• Update the RRM module to enqueue these assets for non-Site Kit users on the edit post page.
• Also enqueue them for non-Site Kit users on the site editor page to prevent potential issues there.
• Complete and merge PR POC to fix RRM blocks in block editor pages for non-Site Kit users. #10401.

Test Coverage

• Add test coverage for the changes to Modules/Reader_Revenue_Manager.

QA

1. In publisher center > RRM, create a publication associated with the test website and configure contribution or subscription payment method.

2. Activate Site Kit and make sure rrmModule and rrmModuleV2 features are enabled.

3. Activate RRM module and connect to the publication for which we have configured payment option above.

4. Go to Posts > Add New, add the block Contribute with Google or Subscribe with Google based on which payment option was configured in publisher center. Save the post.

5. Create a new Editor role user in WordPress and make sure that SK daskboard is not shared with this role.

6. Login with Editor user in new browser window and open the same post in block editor. The Subscribe with Google block should be in disabled state with the same notice as that of AC.

Changelog entry

[nfmohit]

AC ✅

[nfmohit]

IB LGTM ✅

Thank you @techanvil! Please note that I've posted a question in the PoC PR. I feel we can also improve namings and such, but that can be handled during execution.

[techanvil]

Thanks @nfmohit! Great question on the PR, which I've replied to.