[FIX] Run memory leak test separately

[f-dangel]

For unknown reason, running the memory leak test in the same pytest session as the other tests breaks the memory leak detection. The solution is to run this test in a separate pytest session.

Also updates the CI to always run the full test suite so we don't accidentally merge another failure of the full tests into master.

[Copilot]

Pull request overview

This PR addresses a memory leak test detection issue by running the memory leak test in a separate pytest session. The PR modifies test execution to isolate test_memory_leak from other tests, adds debugging output to track memory usage, and simplifies the GitHub Actions workflow configuration.

Key changes:

• Splits test execution into two separate pytest runs: one for test_memory_leak and one for all other tests
• Adds memory usage debugging output to the memory leak detection function
• Simplifies GitHub Actions workflow trigger configuration

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.

File	Description
test/test___init__.py	Added debug print statement and changed loop variable name from _ to s for memory tracking
makefile	Split all test targets to run memory leak tests separately using -k filters
.github/workflows/test.yaml	Simplified workflow triggers and removed conditional test execution logic

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.