Fix a bug where move events were not being consumed properly

When consuming page change events related to page moves, we were applying the moves to the page's history, but we were not consuming the page move, which is a revision in itself.

We now make sure to ingest the move event on process_revisions() only for the latest revision. We want to do this there as that process is optimized for recent data. Later, on process_page_moves() we ingest the same event again, but this time we apply it to all of the pages' revisions. We want to do this there as that process is optimized for touching older data efficiently.

As per our analysis, this should solve about ~55% of the daily inconsistencies.

Bug: T395139