feat: GutenbergKit history navigation

[dcalhoun]

Enable navigating forwards and backwards in the editor history.

Related:

• https://github.com/Automattic/dotcom-forge/issues/9968
• feat: Editor history navigation GutenbergKit#55
• feat: GutenbergKit history navigation WordPress-iOS#23961

To Test:

See wordpress-mobile/GutenbergKit#55.

Regression Notes

1. Potential unintended areas of impact
   None likely, given the changes are scoped to a single editor.
2. What I did to test those areas of impact (or what existing automated tests I relied on)
   N/A.
3. What automated tests I added (or what prevented me from doing so)
   N/A.

PR Submission Checklist:

• I have completed the Regression Notes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Testing Checklist (strike-out the not-applying and unnecessary ones):

• WordPress.com sites and self-hosted Jetpack sites.
• Portrait and landscape orientations.
• Light and dark modes.
• Fonts: Larger, smaller and bold text.
• High contrast.
• Talkback.
• Languages with large words or with letters/accents not frequently used in English.
• Right-to-left languages. (Even if translation isn’t complete, formatting should still respect the right-to-left layout)
• Large and small screen sizes. (Tablet and smaller phones)
• Multi-tasking: Split screen and Pop-up view. (Android 10 or higher)

[dangermattic]

	1 Warning
⚠️	PR is not assigned to a milestone.

Generated by 🚫 Danger

[wpmobilebot]

Project dependencies changes

The following changes in project dependencies were detected (configuration wordpressVanillaReleaseRuntimeClasspath):

list

Upgraded Dependencies
org.wordpress.gutenbergkit:android:55-a490cd3d2d70ad4bba501655f83fdc42b404d502, (changed from v0.0.3)

tree

 +--- project :libs:editor
-|    \--- org.wordpress.gutenbergkit:android:v0.0.3
+|    \--- org.wordpress.gutenbergkit:android:55-a490cd3d2d70ad4bba501655f83fdc42b404d502
-\--- org.wordpress.gutenbergkit:android:v0.0.3 (*)
+\--- org.wordpress.gutenbergkit:android:55-a490cd3d2d70ad4bba501655f83fdc42b404d502 (*)

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21570-ecc0f33
	Commit	ecc0f33
	Direct Download	jetpack-prototype-build-pr21570-ecc0f33.apk

Note: Google Login is not supported on these builds.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Flavor	Jalapeno
	Build Type	Debug
	Version	pr21570-ecc0f33
	Commit	ecc0f33
	Direct Download	wordpress-prototype-build-pr21570-ecc0f33.apk

Note: Google Login is not supported on these builds.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 39.48%. Comparing base (dd12e2f) to head (ecc0f33).
Report is 12 commits behind head on trunk.

Additional details and impacted files

@@           Coverage Diff           @@
##            trunk   #21570   +/-   ##
=======================================
  Coverage   39.48%   39.48%           
=======================================
  Files        2117     2117           
  Lines       99464    99464           
  Branches    15296    15296           
=======================================
  Hits        39269    39269           
  Misses      56714    56714           
  Partials     3481     3481           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nbradbury]

Looks great!

[dcalhoun]

Thank you for the review, @nbradbury. 🙇🏻‍♂️

For future reference, before merging this type of WordPress-Android PR integrating GutenbergKit updates, I typically merge the GutenbergKit PR first and then update this PR to reference the merge commit. This avoids WordPress-Android referencing an orphaned commit. The value of this practice is debatable, but it's a practice I continue from past team guides nonetheless.

It's not a significant issue that we did not do that here, merely sharing for awareness.

[nbradbury]

For future reference, before merging this type of WordPress-Android PR integrating GutenbergKit updates, I typically merge the GutenbergKit PR first and then update this PR to reference the merge commit. This avoids WordPress-Android referencing an orphaned commit. The value of this practice is debatable, but it's a practice I continue from past team guides nonetheless.

A fair point. Perhaps we should add the "Do not merge" label and remove it once the PR is truly ready to merge?

[dcalhoun]

Perhaps we should add the "Do not merge" label and remove it once the PR is truly ready to merge?

Yeah, I can try to do so if it is helpful.

Part of the issue is that I, at times, struggle to remember the merging practices of a given repository I touch, an unfortunate side effect of diverging practices across our various repositories. 😅