fix: pin poetry hook to 2.4.1 to match lock and CI (HYBIM-793)

[fercor-cisco]

Problem

The poetry-lock / poetry-check pre-commit hook is pinned to Poetry 2.2.0, while the committed poetry.lock and CI both use 2.4.1:

Source	Poetry version
.pre-commit-config.yaml (poetry hook rev)	2.2.0
poetry.lock (@generated by Poetry)	2.4.1
.github/workflows/ci-tests.yaml (pipx install poetry==)	2.4.1

Because the hook runs in its own pinned environment, it rewrites poetry.lock's @generated header on every commit, which then gets flipped back by local/CI runs — forcing developers to bypass the hook with git commit --no-verify.

Fix

Bump the hook rev from 2.2.0 to 2.4.1 so it matches the lock-file generator and CI. The 2.4.1 tag was confirmed to exist in python-poetry/poetry.

Scope

This PR intentionally addresses only the Poetry version mismatch. A separate poetry.lock content drift (committed grpcio 1.74.0 vs pyproject.toml's >=1.80.0 constraint) is out of scope and should be handled in its own change.

Verification

• Confirmed 2.4.1 is a valid tag (git ls-remote).
• poetry check passes with local Poetry 2.4.1.
• Ran the hook with rev: 2.4.1: the lock header stays @generated by Poetry 2.4.1 — the version-flip churn is gone.

🤖 Generated with Claude Code