feat(scripts): add script to eslint --fix clients source code

[trivikr]

Issue

N/A

Description

Adds script to eslint --fix source code for clients.

Before

$ time yarn generate-clients
...
Done in 70.78s.
yarn generate-clients  10.71s user 2.41s system 18% cpu 1:10.91 total

After

$ time yarn generate-clients
...
Done in 394.65s.
yarn generate-clients  407.29s user 13.74s system 106% cpu 6:34.78 total

Testing

Verified that source code is linted in #2839

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[trivikr]

This PR can be re-attempted after an option to lint in parallel in introduced in eslint:

• RFC feat: Lint files in parallel if many files exist eslint/rfcs#42
• Issue Lint multiple files in parallel [$500] eslint/eslint#3565

[codecov-commenter]

Codecov Report

Merging #2838 (71a4b0a) into main (7e634cf) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2838   +/-   ##
=======================================
  Coverage   60.42%   60.42%           
=======================================
  Files         554      554           
  Lines       28886    28886           
  Branches     7072     7072           
=======================================
  Hits        17453    17453           
  Misses      11433    11433           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7e634cf...71a4b0a. Read the comment docs.

[trivikr]

This PR can be re-attempted after an option to lint in parallel in introduced in eslint:

• RFC New: Lint files in parallel if many files exist eslint/rfcs#42
• Issue Lint multiple files in parallel [$500] eslint/eslint#3565

Another option is to use @node-rs/deno-lint
Update: deno-lint doesn't support --fix

[trivikr]

Superceded by #2846

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.