[dotnet][rb][java][js][py] Automated Browser Version Update

[selenium-ci]

User description

This is an automated pull request to update pinned browsers and drivers

Merge after verify the new browser versions properly passing the tests and no bugs need to be filed

---

PR Type

Enhancement

---

Description

• Update Firefox browser version from 145.0.1 to 145.0.2

• Update Linux Firefox binary URL and SHA256 checksum

• Update macOS Firefox binary URL and SHA256 checksum

---

Diagram Walkthrough

flowchart LR
  A["Firefox 145.0.1"] -- "version bump" --> B["Firefox 145.0.2"]
  C["linux_firefox archive"] -- "URL & SHA256 update" --> D["Updated linux_firefox"]
  E["mac_firefox archive"] -- "URL & SHA256 update" --> F["Updated mac_firefox"]

Loading

File Walkthrough

	Relevant files
Configuration changes	repositories.bzl Update Firefox pinned browser versions and checksums          common/repositories.bzl Updated Firefox version from 145.0.1 to 145.0.2 for Linux platform Updated Firefox version from 145.0.1 to 145.0.2 for macOS platform Updated corresponding SHA256 checksums for both Linux and macOS binaries Updated download URLs to point to new Firefox release version +4/-4

---

[qodo-merge-pro]

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-merge-pro]

PR Code Suggestions ✨

No code suggestions found for the PR.