Adding in some investigation I did as part of T359990: [SPIKE]Automoderator should log revert conflicts[16H]

Option 1:
Create a unique dashboard per wiki in logstash:

• would require admins to have wikitech login
• if our logging messages ever change then this will no longer work
• harder to view and play around with if you're non-technical
• hard to test
• hard to search for what you want if you don't know how to use opensearch/logstash
• linking to the revision wouldn't be possible
• log retention policy: would we lose potential data? do we care?
• not language agnostic (primarily in english)

Option 2:
On-wiki page that we can append messages to that will inform the admins that a specific revision should have been
reverted but wasn't due to a conflict:

• everyone can see
• not as noisy
• not dependent on a third party tool (opensearch/logstash)
• not dependent on log messages
• ability to make it more user-friendly for non-technical folks
• admins would need to watch the page
• revision history persists in the page's diff history
• wouldn't be searchable/filterable
• can link to a revision like we do in talk page message
• language agnostic

Option 3:
On-wiki page that displays a list of revisions that should have been reverted but weren't due to a conflict
Similar to option 2, except it would be more like a revision history than a talk page message log:

• everyone can see
• not as noisy
• not dependent on a third party tool (opensearch/logstash)
• not dependent on log messages
• ability to make it more user-friendly for non-technical folks
• admins would need to watch the page
• revision history persists in the page's diff history
• would require more design and engineering work than options 1 or 2 but less than 3
• unsure what fields we would care about (revision id, article link, date, etc...) displaying for a revision
• language agnostic

Option 4:
Log-like on-wiki page that displays a list of revisions that should have been reverted but weren't due to a conflict

• everyone can see
• not as noisy
• not dependent on a third party tool (opensearch/logstash)
• not dependent on log messages
• ability to make it more user-friendly for non-technical folks
• admins would need to watch the page
• revision history persists in the page's diff history
• would be searchable/filterable/sortable in the future if we needed
• would require a lot more design and engineering work than all other options
• unsure what fields we would care about (revision id, article link, date, etc...) displaying for a revision
• language agnostic

Option 5:
On-wiki page that displays a change list of revisions that should have been reverted but weren't due to a conflict and renders like Recent Changes, Related Changes, or Watchlist

• everyone can see
• not as noisy
• not dependent on a third party tool (opensearch/logstash)
• not dependent on log messages
• ability to make it more user-friendly for non-technical folks
• admins would need to watch the page
• revision history persists in the page's diff history
• would be searchable/filterable/sortable in the future if we needed
• would require a lot more design and engineering work than all other options
• unsure what fields we would care about (revision id, article link, date, etc...) displaying for a revision
• language agnostic

Backlogging this for now because it isn't a blocker for T370795, and occurrences via T359990 will be extremely unlikely.