chore: add recheck.yaml file for linting

[adamaltman]

What/Why/How?

Adds recheck.yaml configuration file.

This doesn't set up GHA or fix the problems.

Steps

1. Add recheck configuration file
2. Fix problems
3. Set up GHA to prevent future problems

Reference

Testing

Summary

   Breakdown by rule:
   semantic-line-breaks: 1897 (1897 errors)
   bullet-style-dash: 453 (453 errors)
   readable-line-length: 338 (338 warnings)
   optimize-images: 116 (116 errors)
   us-spelling: 99 (99 errors)
   no-gerund-headings: 91 (91 errors)
   no-trailing-spaces: 78 (78 errors)
   no-hard-tabs: 36 (36 errors)
   no-duplicate-headings: 32 (32 warnings)
   no-broken-fragment-links: 8 (8 errors)

Screenshots (optional)

Check yourself

• Code is linted
• Tested
• All new/updated code is covered with tests

Security

• Security impact of change has been considered
• Code follows company security practices and guidelines

[Marshevskyy]

Do you plan to add it in this PR?

[adamaltman]

When I try to fix the errors in the next PR (not this one).

[Marshevskyy]

remove?

[adamaltman]

Probably I'll remove it if I don't need it to fix the errors.

[Marshevskyy]

When is this command run?

[adamaltman]

Right now in my local env. The plan is:

1. Add recheck configuration file
2. Fix problems
3. Set up GHA to prevent future problems

But I want to make it easy for someone to remember how to run recheck because they may not remember the command name run or the options which I always tend to use --stats.