[py] Update dev dependencies to fix vulnerability

[cgoldberg]

🔗 Related Issues

Fixes https://github.com/SeleniumHQ/selenium/security/dependabot/245
Fixes https://github.com/SeleniumHQ/selenium/security/dependabot/246

💥 What does this PR do?

This PR updates dev dependencies and the lock file.

🔄 Types of changes

• Dev/CI/Security

[qodo-code-review]

PR Type

Bug fix

---

Description

• Update cryptography from 46.0.4 to 46.0.5 to fix security vulnerability

• Update cachetools from 7.0.0 to 7.0.1 for dependency maintenance

• Update lock file hashes to match new package versions

---

File Walkthrough

Relevant files

Dependencies

requirements.txt Update cryptography and cachetools versions                            py/requirements.txt Bump cryptography from 46.0.4 to 46.0.5 Bump cachetools from 7.0.0 to 7.0.1 +2/-2      requirements_lock.txt Update locked dependency hashes                                                    py/requirements_lock.txt Update cachetools hashes for version 7.0.1 Update cryptography hashes for version 46.0.5 (56 hash entries) +53/-53

---

[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.