[github-actions]

Automated dependency update for poetry.lock.
This PR was created by the workflow dependency-update.yml

Remaining vulnerable dependencies after the automated update:

[
  {
    "name": "filelock",
    "version": "4.1.0",
    "vulnerability": "CVE-2026-112906",
    "fix_versions": [
      "4.2.1"
    ]
  },
  {
    "name": "filelock",
    "version": "4.1.0",
    "vulnerability": "CVE-2026-112940",
    "fix_versions": [
      "4.2.1"
    ]
  },
  {
    "name": "filelock",
    "version": "4.1.0",
    "vulnerability": "CVE-2026-112914",
    "fix_versions": [
      "4.2.1"
    ]
  },
  {
    "name": "filelock",
    "version": "4.1.0",
    "vulnerability": "CVE-2026-112913",
    "fix_versions": [
      "4.2.1"
    ]
  },
  {
    "name": "filelock",
    "version": "4.1.0",
    "vulnerability": "CVE-2026-112937",
    "fix_versions": [
      "4.2.1"
    ]
  },
  {
    "name": "filelock",
    "version": "4.1.0",
    "vulnerability": "CVE-2026-112907",
    "fix_versions": [
      "4.2.1"
    ]
  }
]

[ArBridgeman]

Handling in #980
as to truly have all Python version non-vulnerable isn't possible as latest filelock only for Python 3.11+