[mfazekas]

Description

The nightly doc screenshot run now refreshes the doc site's example screenshots through a reviewable maps-docs PR instead of them going stale. A new job compares the captured screenshots with maps-docs main and copies only those that changed by more than 0.5% of the pixels (status bar ignored), plus new examples; screenshots of removed examples are dropped and screenshots.json is kept in sync. Unchanged images stay byte-identical. If anything changed it force-pushes a single commit on top of maps-docs main to auto/example-screenshots with the existing deploy key; rnmapbox/maps-docs#16 opens/updates the PR from that branch.

excludeFromPercy examples differ by 2-80% between runs (measured on three recent captures), so no threshold separates real changes from noise; they are only replaced when new, when the screenshot size changes, or when the workflow is dispatched with refresh_unstable.

Tested with a temporary push trigger that reused the doc-screenshots artifact of run 39746036267: the job pushed the branch with the deploy key, the maps-docs workflow opened a PR, a rerun detected the branch was up to date, and a further push updated the PR body. Test branches and PR are deleted.

Checklist

• I've read CONTRIBUTING.md
• I updated the doc/other generated code with running yarn generate in the root folder
• I have tested the new feature on /example app.
• I added/updated a sample - if a new feature was implemented (/example)