Feature: Use pre-commit.ci

Currently we use the following in our ci workflow

      - name: Execute pre-commit handler
        continue-on-error: true
        run: |
          poetry run pre-commit run check-toml
          poetry run pre-commit run trailing-whitespace
          poetry run pre-commit run end-of-file-fixer
          poetry run pre-commit run ruff
          poetry run pre-commit run ruff-format
      - name: Execute mypy
        run: |
          make mypy-core-report
          make mypy-core

So we run all hooks but the mypy hool and then run mypy.

I suggest we use https://pre-commit.ci/

This service run the pre-commit hooks and offers a skip option for ci, so we have one file where to define which hooks should run in ci and locally.

It also has speed advantages and can commit changes of ruff back to MR.
It also updates the pre-commit file automatically, creating a PR.

首先检查当前的 CI 工作流和仓库的 pre-commit 配置，重点关注列出的 hook 以及单独的 mypy 命令。确认 pre-commit.ci 的 CI 跳过选项如何适配现有工作流；当这些 hook 已针对本地使用和 CI 使用进行一致定义，且 mypy 仍能成功运行时，即视为完成。