Description

Related Issue: CC #184

Pre-commit steps

• Tested on QEMU and real HW Rasperry Pi.
  • Not needed if it is just a README change or similar.
• Ran ./contributor_setup.sh followed by ./devtool ready_for_publish
  • You'll need Ruby with Bundler and NPM installed locally.
  • If no Rust-related files were changed, ./devtool ready_for_publish_no_rust can be used instead (faster).
  • This step is optional, but much appreciated if done.

What did this PR do

1. Main reason: Because every time a PR is submitted during the translation of a chapter, a Github CI check will be conducted and an error will be reported.
2. Solution: Fix Github CI running errors.

The following things were done to fix this error:

1. Modified the year check error, many files have a deadline of 2022, which can cause Github CI to make errors when running bundle exec ruby utils/devtool.rb copyright.
2. Modified the settings.json file and add prettierrc. json. If the code format is not followed, it will cause Github CI to run error when running bundle exec ruby utils/devtool.rb fmt_check.
3. Revised Ruby code format (method comments) to include i.to_s ->i It does not need to be called explicitly, which will cause Github CI to error when running bundle exec ruby utils/devtool.rb rubocop

Because I need to check many files, I cannot manually modify them one by one. I will replace them in bulk and finally convert the code format.

CC @eldruin @andre-richter