fix(deps): update dependency ch.qos.logback:logback-classic to v1.5.20

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ch.qos.logback:logback-classic (source, changelog)	1.5.19 -> 1.5.20

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	9feab0a
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/69036f7d2d6c4d0008de3e4e
😎 Deploy Preview	https://deploy-preview-2521--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[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: No functional code: The PR only updates a dependency version in the POM and adds no runtime code, so audit trail compliance cannot be assessed from the diff. Referred Code <logback.version>1.5.20</logback.version>
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: No identifiers added: Only a version property value was changed with no new code or identifiers, so naming conventions cannot be evaluated. Referred Code <logback.version>1.5.20</logback.version>
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: No error paths: The diff only updates a dependency version in build config and introduces no executable logic to assess error handling. Referred Code <logback.version>1.5.20</logback.version>
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: No user errors: No user-facing error handling code was added or modified; changing a dependency version does not expose error messages to assess. Referred Code <logback.version>1.5.20</logback.version>
	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: Dependency update: The change only bumps logback.version to 1.5.20 without altering application logging code, so secure logging practices cannot be verified from this diff. Referred Code <logback.version>1.5.20</logback.version>
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: No input handling: No code paths handling external inputs were added or changed; only a dependency version property was updated, so validation practices cannot be assessed. Referred Code <logback.version>1.5.20</logback.version>

Compliance status legend

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