In order to parse the amount of errors Checkstyle finds, we need to tell
the parser which type of message the linter responds with.
In case of checkstyle, it has a message like Checkstyle ends with
([0-9]+) errors which corresponds to `regex_number`. Otherwise
megalinter will respond always with 1.

* Update StandardJS VS Code extension identifier

The original extension has been deprecated:

> ⚠️ Warning: This extension version is not actively being maintained. There is a new version published under the `standard` namespace, please install the new version: https://marketplace.visualstudio.com/items?itemName=standard.vscode-standard also available on open-vsx registry: https://open-vsx.org/extension/standard/vscode-standard

* Update CHANGELOG.md

* Update mega-linter-runner v6 pre-commit hook docs.

When the pre-commit hooks were updated from v5 to v6, the corresponding
documentation in the auto-generated docs/mega-linter-runner.md was
updated by mistake, so the documentation was immediately overwritten.
Update the source file mega-linter-runner/README.md instead this time.

* Run MegaLinter pre-commit hooks serially (#1826).

MegaLinter runs linters in parallel. Instruct pre-commit not to run
multiple instances of MegaLinter itself to prevent fork-bombing. This
also prevents the megalinter-full hook from redundantly running each
project linter once per MegaLinter invocation, which is both wasteful
and can lead to race conditions.

Co-authored-by: Nicolas Vuillamy <nicolas.vuillamy@gmail.com>

* Convert SARIF to human readable text v0

* Build

* Use stdout_human when necessary

* use rustup sh to install rust

* Fix call to sarif-fmt

* flake8 fix

* [MegaLinter] Apply linters fixes

* changelog

* [MegaLinter] Apply linters fixes

Co-authored-by: nvuillam <nvuillam@users.noreply.github.com>