Well, I spoke with @ormsbee about this. There seemed to be a mistake in a previous change which did not remove these migration steps. This meant I couldn't actually run my work locally as when I applied the migrations, I got an error regarding dropping a table that did not exist. Dave O and @jbau (I think) recommended that I manually remove this.

I agree that ideally this would be good as a separate PR, but I'm not sure how I could manage the workflow as that would would have to get merged in before I can take that on.