[CI] Split backend unit and integration suites into separate jobs for faster triage

[utksh1]

Summary

The backend CI job currently runs the full test suite in one block, which makes failure triage slower than necessary.

Scope

• Separate unit and integration coverage into distinct jobs or phases.
• Keep dependency installation overhead reasonable.
• Preserve the current benchmark exclusion behavior.

Acceptance criteria

• Unit and integration failures are distinguishable in CI.
• Job structure still fits current dependencies.
• Contributor feedback becomes easier to interpret.

[anshul23102]

Interested in contributing to this under NSoC'26. This is a valuable issue addressing important functionality/quality. Happy to take this on.

/assign

[anshul23102]

Interested in contributing under NSoC'26. This is a valuable issue. Happy to work on it.

/assign

[nensii21]

@utksh1 /assign

[jyotsnak1603]

Hi @utksh1,

I would like to work on this issue under GSSoC 2026.

I reviewed the requirements and understand that the goal is to improve CI feedback by separating backend unit and integration test execution into distinct jobs or phases while preserving the current dependency setup and benchmark exclusion behavior. My approach would be to analyze the existing workflow configuration, split the test suites into clearly identifiable CI stages, and verify that failures are reported independently for faster debugging and contributor feedback.

I have experience working with GitHub Actions, CI/CD workflows, and test automation, and I would be happy to contribute this improvement.

Could you please assign this issue to me?

Thank you.