Fix violations against core eslint rules

Here's a first pass. Let's see what the bot says about this.

Disabled cspell from some of the generated files.

🙄

😓

How much effort should we put into researching the root cause for that? We haven't updated the yarn.lock since late June and there must be some updates to dependencies of our dependencies that cause these changes. Most of these changes happen automatically as a result of running yarn install in js/admin.

Did a bit of digging and it seems like most of the changes are caused by something changing in yarn, which is changing the order of the keys in yarn.lock.

Most of the fixes are coming from running yarn lint:core-js-passing --fix. However, there were manual changes required to make yarn lint:core-js-passing pass because the eslint violation fixer doesn't fix violations that have an impact on code logic. That said, all changes in the patch are required to either make yarn lint:core-js-passing or the CI cspell pass.