chore: upgrade actions/checkout from v4 to v5

[luojiyin1987]

User description

Update all GitHub Actions workflows to use actions/checkout@v5 for improved security and performance.

---

PR Type

Enhancement

---

Description

• Upgrade actions/checkout from v4 to v5 across all workflows

• Improves security and performance of GitHub Actions

• Updates five workflow files consistently

---

Diagram Walkthrough

flowchart LR
  A["GitHub Actions Workflows"] -- "upgrade checkout version" --> B["actions/checkout@v5"]
  C["v4"] -- "replaced by" --> B
  B -- "applied to" --> D["5 workflow files"]

Loading

File Walkthrough

Relevant files

Dependencies

build-and-test.yaml Upgrade checkout action to v5                                                        .github/workflows/build-and-test.yaml Updated actions/checkout from v4 to v5 Maintains all other workflow configuration unchanged +1/-1      code_coverage.yaml Upgrade checkout action to v5                                                        .github/workflows/code_coverage.yaml Updated actions/checkout from v4 to v5 Maintains all other workflow configuration unchanged +1/-1      docs-ci.yaml Upgrade checkout action to v5                                                        .github/workflows/docs-ci.yaml Updated actions/checkout from v4 to v5 Maintains all other workflow configuration unchanged +1/-1      e2e_tests.yaml Upgrade checkout action to v5                                                        .github/workflows/e2e_tests.yaml Updated actions/checkout from v4 to v5 Maintains all other workflow configuration unchanged +1/-1      pre-commit.yml Upgrade checkout action to v5                                                        .github/workflows/pre-commit.yml Updated actions/checkout from v4 to v5 Maintains all other workflow configuration unchanged +1/-1

---

[qodo-merge-for-open-source]

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
🟢	Consistent Naming Conventions Objective: All new variables, functions, and classes must follow the project's established naming standards Status: Passed
	No Dead or Commented-Out Code Objective: Keep the codebase clean by ensuring all submitted code is active and necessary Status: Passed
	Robust Error Handling Objective: Ensure potential errors and edge cases are anticipated and handled gracefully throughout the code Status: Passed
	Single Responsibility for Functions Objective: Each function should have a single, well-defined responsibility Status: Passed
	When relevant, utilize early return Objective: In a code snippet containing multiple logic conditions (such as 'if-else'), prefer an early return on edge cases than deep nesting Status: Passed

Compliance status legend

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

[qodo-merge-for-open-source]

PR Code Suggestions ✨

No code suggestions found for the PR.