fix: don’t convert VersatileImageField to ForeignKey

The image attributes on our models were using VersatileImageField before
our migration to a separate image model. VersatileImageField uses a
VARCHAR field internally that cannot be converted to a ForeignKey.

Signed-off-by: Ernesto Rico Schmidt <ernesto@helsinki.at>