setup typos check in CI (for rust repo)

[klensy]

Proposal

Add step to rust CI to check code/comments for typos, to keep things clean.

There was previous attempts to add this (links?), but they produced a lot of false positives. PR (rust-lang/rust#134006) adds that check and also contains (https://github.com/rust-lang/rust/blob/16ab024f2546607eb3f3aa3aa96eb3e382c442f5/typos.toml) short'ish exclusion list, so maintaining it should not be painful.

Currently implemented for: compiler, library, bootstrap, librustdoc.

Spellcheck did not break any other jobs on fail, it run separately and and results available in ~ 20 seconds.

Mentors or Reviewers

If you have a reviewer or mentor in mind for this work, mention them
here. You can put your own name here if you are planning to mentor the
work.

Process

The main points of the Major Change Process are as follows:

• File an issue describing the proposal.
• A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
  • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
  • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
• Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

[rustbot]

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

Concerns or objections to the proposal should be discussed on Zulip and formally registered here by adding a comment with the following syntax:

@rfcbot concern reason-for-concern 
<description of the concern> 

Concerns can be lifted with:

@rfcbot resolve reason-for-concern 

See documentation at https://forge.rust-lang.org

cc @rust-lang/compiler

[BoxyUwU]

@rfcbot concern contributor friction

[nnethercote]

@rustbot second

[apiraino]

@rfcbot resolve contributor friction

As per discussion https://rust-lang.zulipchat.com/#narrow/channel/233931-t-compiler.2Fmajor-changes/topic/setup.20typos.20check.20in.20CI.20.28for.20rust.20repo.29.20compiler-team.23817/near/501792173

[apiraino]

@rustbot label -final-comment-period +major-change-accepted

[apiraino]

@rfcbot concern contributor friction

Reverting accepted status because this concern is not addressed