Incomplete JPEG writing after libjpeg-turbo 3.0.0 upgrade

There is a bug in libjpeg-turbo 3.0.0 where not all data is written when `WITH_SIMD` is not defined. I think to encounter the bug it must be a 64-bit platform without NEON extensions. Because it is related to an uninitialized variable, it doesn't occur 100% of the time, but it can result in a truncated JPEG file.

Opening the file afterward results in `Corrupt JPEG data: premature end of data segment` warnings and a small amount of missing data at the end of the file (usually manifests as a small rectangle of grey in the corner of the image).

I have reported the libjpeg-turbo issue here:

https://github.com/libjpeg-turbo/libjpeg-turbo/issues/728