Add typos tool to CI to automate typo detection

Motivation: Since recently more projects are starting to do airdrops and using lists of repositories to reward contributors (eg. Namada, StarkWare, etc), a new wave of airdrop farmers has emerged, no longer collecting discord chat points but now going after code contributions. In the era of bots and automation, we must protect humans attention and time, and in this case we can avoid spending time on airdrop-farmers PRs that could simply be avoided by having our own automated tool.

This has been already a problem to other projects, we were postponing it but seems that we are now target too: https://github.com/privacy-scaling-explorations/folding-schemes/pull/75

There are now even twitter tutorials on how to farm contributions: https://twitter.com/Abrahamchase09/status/1759101213381959960 , which has their results: https://twitter.com/toghrulmaharram/status/1759228275228905511 .

A solution could be from time to time do a PR fixing all typos, as done here: https://github.com/risc0/risc0/pull/1319 , but this does not prevent future typos from happening.

What this PR does: Add GitHub CI that runs typos so future PRs will run the typos check to detect typos. Also this PR fixes the detected typos.

About the tool:

Tried cspell (typescript) , and it has too many false-positives (thousands) for custom variable names that we don't consider them typos (eg. Multilinear, evals, arkworks, thiserror, Circom, biguint, nbits, ... and a thousand more), since it works with a dictionary of correct words approach.
Then with typos (rust), since it does not work with a dictionary of correct words but with a dictionary of typos corrections, it does not have the false positives that cspell has. The downside of this approach is that it might not recognize typos that are not yet in their list, but it can easily be updated.

Hey!

I totally approve of your idea to automate typo detection. I have even personally suggested it to folks in the past.

But you have totally misunderstood my intentions here. Since you have taken the time to go through my recent PR contributions, I would suggest that you go back and check all my PR contributions AND bug reports over the years.

While you will find many typo fixing PRs as it's a low hanging fruit and I'm not a developer but a tech fan and I do it just for fun, you will also find that I have contributed in very diverse projects that have no connection to crypto whatsoever. So if my intention would be to farm PRs why would I waste my effort and contribute to projects I have nothing to gain from? The answer is that I do it only for projects I like for different reasons and it's my way to say thanks to the developers.

But after reading your reasoning, I do see why you would think I am a "PR farmer". By the way, this is the first time I stumble upon this term!

Anyway, no hard feelings and keep doing what you are doing :)

privacy-scaling-explorations / sonobe

Add typos tool to CI to automate typo detection #76