fix: stricter linting across repo

[iamacook]

What it solves

Lax linting/prettier

How this PR fixes it

The whole project is now checked for lint and automatically prettified. The linting rules were made stricter.

We should ideally remove '@typescript-eslint/no-explicit-any' as well as enable the default React linter but this resurrected >100 warnings of non/false-typed code and typing this manually started to get out of hand. I have a local stash of this locally but it became quickly apparent that this would like cause bugs/require a full regression.

For now, the added rules and project-wide scanning should improve our committed code.

How to test it

• Commit unformatted code and see it get automatically 'prettified'
• Attempt to commit code that goes against our rules and observe a warning that prevents pushing

[github-actions]

CLA Assistant Lite All Contributors have signed the CLA.

[github-actions]

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type	Occurrences	Fixable
Errors	0	0
Warnings	0	0
Ignored	0	N/A

• Result: ✅ success
• Annotations: 0 total

---

^{Report generated by eslint-plus-action}

[coveralls]

Pull Request Test Coverage Report for Build 2219557523

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 35.575%

---

Totals
Change from base Build 2208794601:	0.0%
Covered Lines:	3541
Relevant Lines:	9005

---

💛 - Coveralls

[github-actions]

Deployment links

🟠 Rinkeby	⚪ Mainnet	🟣 Polygon	🟡 BSC	⚫ Arbitrum	🟢 Gnosis Chain

[katspaugh]

Cool, thank you Aaron!

[iamacook]

I'm going to directly merge this as it's purely dev relevant.