[CLEANUP] Fix typos across the project

[Wheest]

Feel free to close this PR and add the fixes in a more substantial commit.

This PR is just to highlight the typos.

[Jokeren]

I'd suggest using something like codespell to check and fix all typos in a single PR

[Wheest]

Thanks!

I've done this, as I've been looking for an excuse to dive deeper into the codebase.

This PR should now be slightly more useful, as it corrects dozens of spelling errors, rather than just a couple. I squashed all my commits into a single one.

I was conservative in my correction criteria:

• codespell provided suggestions, but I used my own discretion when applying them
• I ignored anything in the third-party directory
• Corrections were only on comments and docs, no code (even if a variable name was clearly a typo). Exceptions to this include:
  • An error message string in AxisInfo.cpp:995
  • An error message string in hip.c:15
  • An error message string in WSPipeline.cpp
  • Docstrings in tablegen files (still documentation, but is compiled)

I'm happy to expand this PR to include additional "quality of life" improvements that the team hasn't prioritized.

[Jokeren]

What're "quality of life" improvements?

[ThomasRaoux]

I think this is a nice cleanup in itself

[Wheest]

Thank you both!

@Jokeren, by QoL improvements, I mean things like:

• Code Refactoring: any known places were Foo is implemented in a few ways, which could be unified, or a given Foo is overcomplicated?
• CI/CD improvements: it seems like clang-format etc is already set up, but maybe support for additional targets, or updating build dependencies needs to be done?
• Testing: tests seems to be pretty extensive, but perhaps there's some known edge cases that could be added (e.g., in TVM I fixed support for conv2d asymmetric padding & dilation).

Essentially anything that's suitable for a new contributor. I'll also look under the "help wanted" issue label.