The recently_reset column in the users table was originally supposed to be dropped back in late 2018, but the migration slipped through the cracks, and was marked as having been run even though it never was. Then, in 2019, the schema and structure files were regenerated from production, resulting in both files (a) including the recently_reset column, and (b) falsely marking the 2018 migration as having been run.
In order to make sure that the column is dropped both in production and in the automated tests, the old migration needs to be redated to 2020, and modified to include the pt-online-schema-change command.
Testing Instructions: No manual testing needed. This column hasn't been used in over a year.