Add unicorn rules to autofix code style concerns

We have some more devs on, and I just (blessedly) noticed someone else nit `.forEach()` => `for..of`.

Using unicorn _**autofix**_ rules to refactor on commit (ESLint + husky, and in IDE using formatter) was downright magical after adding to litegraph. I would heartily recommend adopting it.

Downside? Usage search shows 140 results in 64 files to be changed.

┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-5331-Add-unicorn-rules-to-autofix-code-style-concerns-2646d73d3650813aacd9d5b40714c7c0) by [Unito](https://www.unito.io)

Start by reviewing the repository's ESLint configuration and the 140 usage-search results across 64 files mentioned in the issue. Determine which Unicorn autofix rules are intended, apply them through the existing commit and formatter workflows, and verify that the reported code-style concerns are resolved without introducing new failures.

Written by the indexing model from the issue text.