Reapplies DependencyUpdates changes off recent dev

[drolsen]

This is a re-application of the work done by @bstaruk: https://github.com/connectivedx/fuzzy-chainsaw/pull/321

We had a slip-up last week where a revert of the original merge request was only merged, not the actual work. Revert was not because of any work done, but because of an additional review request was made.

That being said, @bstaruk

Description

• New branch off recent develop
• Merged changes in by hand

@bstaruk I did leave a few changes out due to new styleguide updates:

• https://github.com/connectivedx/fuzzy-chainsaw/pull/321/files#diff-adfbd64070dedc61b87a1cccf331461f
• https://github.com/connectivedx/fuzzy-chainsaw/pull/321/files#diff-7d9bd41bb1eec59f2b1fb07b56c86de9
• https://github.com/connectivedx/fuzzy-chainsaw/pull/321/files#diff-a16072fd4e75206c9da85cb7f21d92a3

Please let me know if these still need to be applied. Thanks!

Motivation and Context

Clean up our dependencies and resolve latest eslint version warnings / errors.

How Has This Been Tested?

Ran:

• npm or yarn dev
• npm or yarn build
• npm or yarn production
• npm or yarn watch

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] All new and existing tests passed.