Add editor onboarding capability

[dcalhoun]

• Gutenberg: Add editor onboarding capability WordPress/gutenberg#31349
• WPiOS: Add editor onboarding capability WordPress-iOS#16406
• WPAndroid: Add editor onboarding capability WordPress-Android#14558

Add editor onboarding capability to control visibility of the feature. The flag combines (A) if the user has previously launched the Gutenberg editor and (B) if the user ID falls within the percentage of users allowed.

This flag is the first task of several to control when the editor onboarding is displayed. This flag will be used in combination with other, future flags (e.g. tooltipsSeen tracking which tips have been shown) to determine what should be displayed.

// If the user is eligible to begin onboarding...
if (canViewEditorOnboarding) {
  // Display first tooltip
}

// The user began onboarding, but has not yet seen the second tooltip...
if (tooltipsSeen.length > 1 && !tooltipsSeen.includes('tooltip2')) {
  // Display second tooltip
}

To test:

As this PR and its siblings contain no user-facing changes, the following test plan involves logging out the newly added capability to ensure it is working properly. The value behind shipping this addition on its own is to (A) begin tracking editor launches sooner rather than later and (B) produce smaller code diffs to review.

Patch to log editor onboarding flag

diff --git a/packages/block-editor/src/components/inserter/index.native.js b/packages/block-editor/src/components/inserter/index.native.js
index 463e03c116..9c3a023466 100644
--- a/packages/block-editor/src/components/inserter/index.native.js
+++ b/packages/block-editor/src/components/inserter/index.native.js
@@ -325,7 +325,12 @@ export default compose( [
 
 			const {
 				__experimentalShouldInsertAtTheTop: shouldInsertAtTheTop,
+				canViewEditorOnboarding,
 			} = getSettings();
+			console.log(
+				'>>> canViewEditorOnboarding',
+				canViewEditorOnboarding
+			);
 
 			// if post title is selected insert as first block
 			if ( shouldInsertAtTheTop ) {

1. Create a patch file on your local system from the diff above.
2. Clone this gutenberg-mobile branch.
3. cd gutenberg && git apply path/to/patch-file.diff && cd ..
4. Run the Metro server.
5. Clone the corresponding branches for WPAndroid and WPiOS, run the main apps leveraging this branch via the integration guides for WPAndroid and WPiOS respectively.
6. Launch the editor.
7. Expected: >>> canViewEditorOnboarding true is logged in the Metro server as it is the first time the editor has launched.
8. Close the editor.
9. Launch the editor.
10. Expected: >>> canViewEditorOnboarding false is logged in the Metro server for all editor launches moving forward.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

[dcalhoun]

@jhnstn I debated as to whether we should attempt to merge these changes on their own or combine them with the first user-facing feature (i.e. the “Tap to add content” tooltip). I ultimately decided to proceed with opening a PR as-is. Because of this, the test plan is a bit more manual. I figured it might be better to receive your feedback sooner rather than later and also keep the code review focused on a smaller amount of changes.

Let me know if believe it makes more sense to wait to merge this work until we complete the first tooltip. Regardless, I'd still appreciate your input on the approach thus far. Thanks!

[jhnstn]

@dcalhoun I like shipping this change now before we get into the UI work.

[jhnstn]

Gutenberg PR approved 👍