tests: testing all with ignore pattern

[Borda]

Before submitting

• Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure to update the docs?
• Did you write any new necessary tests?

What does this PR do?

Ensure that all tests are executed, addresses #620 (comment)
fused together with #678

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.

Did you have fun?

Make sure you had fun coding 🙃

[Copilot]

Pull Request Overview

This PR modifies the CI testing workflow to ensure all tests are executed by changing the test discovery approach. Instead of explicitly listing specific test directories and files, it now runs pytest on the entire repository with ignore patterns for directories that should be run separately.

• Simplified test execution by using pytest discovery on the entire repository
• Added ignore patterns to exclude processing and raw test directories from parallel execution
• Added documentation comment to clarify the relationship between ignored and separately executed tests

[Borda]

@deependujha lets try increase to -n 4

[deependujha]

github ci has 2 cpus only. So I stayed with -n 2. Let's see how it goes.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84%. Comparing base (2ba36e7) to head (c4b409b).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@         Coverage Diff         @@
##           main   #679   +/-   ##
===================================
  Coverage    84%    84%           
===================================
  Files        52     52           
  Lines      7021   7021           
===================================
+ Hits       5902   5903    +1     
+ Misses     1119   1118    -1     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.