The reason for removing this migration is that the migration was not
isolated (because of its complexity) and we want to minimize the risk of
causing additional problems (as the migration is dependent on actual
model).

For compatibility reasons this migration is just made no-op.