Add a way to see edits/revisions that are likely to be related

### Problem

### A clear and concise description of what you want to happen

Being able to look at a history (e.g., ) and have some way to see (possibly) related edits (e.g., by the same editor/account + within a short timeframe (seconds?)).

### Expected behaviour / screenshots (ex: Figma design screenshots for UI feature)

### Additional Context

This could be one more tool, along with https://github.com/internetarchive/openlibrary/issues/8709, to figure out the provenance of entities when figuring out whether entities should be merged or split or otherwise dealt with in some way.

### Proposal & Constraints

### What is the proposed solution / implementation?

Add a link on `?m=history` pages for each revision that will show edits/revisions done by the same account within a short timeframe, which can probably be considered in seconds (esp. for bots that might be doing 100s of edits/minute).

### Is there a precedent of this approach succeeding elsewhere?

MusicBrainz and BookBrainz have a rich editing history (and search!). This would not come close to this, but it would be one step towards being able to better use the revision history when investigating items.

### Which suggestions or requirements should be considered for how feature needs to appear or be implemented?

Access should be only for librarians and higher.
Figure out what time interval to look at (possibly make it customisable?).

### Leads

### Related files

### Stakeholders

---

### Instructions for Contributors

- Please [run these commands](https://github.com/internetarchive/openlibrary/wiki/Git-Cheat-Sheet#working-on-your-branch) to ensure your repository is up to date **before** [creating a new branch](https://github.com/internetarchive/openlibrary/wiki/Git-Cheat-Sheet#making-changes-and-creating-a-pull-request) to work on this issue and **each time after** pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.