Upgrade nearly-all dev deps

[crutchcorn]

What's Changing and Why

Upgrading dev deps, there should be no breaking changes to consumption

The only three dev deps were not updated were:

• @types/yargs - seemed to break some type checks on CLI when doing so
• ts-node - seemed to break some things in a build step when doing so, I know some tools rely on this via peer dep, so I assumed not upgrading for now would be best
• @types/log-symbols - v3 turns into a shim type as v3 of the library added TS support https://github.com/sindresorhus/log-symbols/releases. However, v3 of the library also ups the required node version, which would mean a breaking change for jimp that I didn't want to introduce until more work on Uncaught ReferenceError: regeneratorRuntime is not defined #797

I also had to run xo --fix to fix some things that were added/changed somewhere in the linting process when upgrading eslint, prettier, I'm unsure

What else might be affected

This would drop support for any version of node > 8 for local dev

There seem to be new warnings for linting, but no errors

Published PR with canary version: 0.8.5-canary.799.447.0

[crutchcorn]

@hipstersmoothie seems there is some issue with auto being released as-of-7.5 or 7.6. Seeing how you contributed to 7.4 I figured I'd give you a heads up before reverting it:

https://circleci.com/gh/oliver-moran/jimp/412

[hipstersmoothie]

🚀 PR was released in v0.8.5 🚀

[crutchcorn]

@hipstersmoothie I don't mean to complain too much, but the CHANGELOG.md seems to have associated this PR as well as #800 to @popinguy

https://github.com/oliver-moran/jimp/blob/master/CHANGELOG.md#v085-fri-oct-18-2019

(The same on the Releases tab)