chore(ci): limit unit test duration to 45minutes

[LesnyRumcajs]

Summary of changes

Changes introduced in this pull request:

• we don't want the unit tests to run for too long; if they do, there is an issue. Let's limit them to 45 minutes.

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Outside contributions

• I have read and agree to the CONTRIBUTING document.
• I have read and agree to the AI Policy document. I understand that failure to comply with the guidelines will lead to rejection of the pull request.

Summary by CodeRabbit

Release Notes

• Chores
  • Improved test pipeline stability by extending the maximum execution timeout for release tests, ensuring adequate time for test completion.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

A 45-minute timeout limit is added to the tests-release job in the unit-tests GitHub Actions workflow, extending the maximum execution time allowed for the job to complete.

Changes

Cohort / File(s)	Summary
GitHub Actions Configuration .github/workflows/unit-tests.yml	Added timeout-minutes: 45 parameter to the tests-release job to extend maximum execution time.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• akaladarshi
• sudo-shashank

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding a 45-minute timeout limit to the unit tests CI job in the GitHub Actions workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch limit-unit-test-duration

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}