Add sha field for existing background migration
What does this MR do?
We forgot to add sha_attribute :location_fingerprint
for !40497 (merged) migration. As a result location_fingerprint column updated without proper serialisation.
This MR
- Fixes bug
- Creates new migration,
- No ops for buggy migration
- Adds regression test
Estimations and explain statements will be the same as !40497 (merged) migration.
Does this MR meet the acceptance criteria?
Conformity
Edited by Can Eldem