chore: update repo migration status after every possible error during import

I noticed we were not updating it in two spots, which are very unlikely to ever trigger, but nevertheless worth covering.