[py] Bump versions of ruff and mypy for Dev/CI

[cgoldberg]

User description

💥 What does this PR do?

This PR bumps the versions of ruff (linting/formatting) and mypy (type checking) to the latest versions in tox.ini, and updates the version and hashes for ruff in multitool.lock.json for use by Bazel.

🔄 Types of changes

• Dev/Build/CI

---

PR Type

Enhancement

---

Description

• Bump ruff from 0.14.2 to 0.14.7 for linting/formatting

• Bump mypy from 1.18.2 to 1.19.0 for type checking

• Update ruff binary hashes in multitool.lock.json for all platforms

• Maintain consistency across dev/CI tooling versions

---

Diagram Walkthrough

flowchart LR
  A["tox.ini"] -->|ruff 0.14.2 to 0.14.7| B["Updated versions"]
  A -->|mypy 1.18.2 to 1.19.0| B
  C["multitool.lock.json"] -->|Update ruff binaries & hashes| B
  B -->|All platforms| D["Linux, macOS, Windows"]

Loading

File Walkthrough

Relevant files

Dependencies

tox.ini Bump ruff and mypy tool versions                                                  py/tox.ini Upgrade ruff from 0.14.2 to 0.14.7 Upgrade mypy from 1.18.2 to 1.19.0 Updates dev/CI linting and type-checking tool versions +2/-2      multitool.lock.json Update ruff binary versions and checksums                                multitool.lock.json Update ruff release version from 0.14.2 to 0.14.7 across all platform binaries Update SHA256 hashes for Linux ARM64, Linux x86_64, macOS ARM64, macOS x86_64, and Windows x86_64 binaries Maintain Bazel multitool lockfile consistency with latest ruff release +10/-10

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.