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 設定を確認し、一覧にあるフックと分離された mypy コマンドに重点を置きます。pre-commit.ci の CI スキップオプションが既存のワークフローにどのように適合するかを確認します。フックがローカルと CI で一貫して使用できるように定義され、mypy も引き続き正常に実行されれば完了です。