reversing default state of createNoScaleImage flag

The ```createNoScaleImage``` flag is defined as: 
> whether to create files if upscale is set to false and large sizes are specified

The existing logic didn't consider if ```upscale``` was set to _false_ and created the files when ```createNoScaleImage``` was set to false

This commit makes small tweaks so the flag behaves as outlined. 

The default state of the flag is reversed so the default behavior remains the same. The biggest impact will be wherever the flag is manually set on the application level.