Refactor task execution system: improve call stack management

[catrielmuller]

Related GitHub Issue

Related: #5601

Description

Refactors the recursive recursivelyMakeClineRequests method to use an iterative stack-based approach to prevent potential stack overflow issues and memory leaks.

On some scenarios like a long task continue execution, a deep call stack can cause performance degradation and unnecessary open functions that prevent the run of the GC properly.

Implementation

• Memory Leak Fix: Enhanced Task.dispose() method with event listener cleanup
• Added periodic yielding in task processing loops
• Transformed recursivelyMakeClineRequests() from recursive to iterative implementation
• Added Nix flake configuration for development environment

Test Procedure

#5601

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Testing: New and/or updated tests have been added to cover my changes (if applicable).
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Documentation Updates

Does this PR necessitate updates to user-facing documentation?

• No documentation updates are required.
• Yes, documentation updates are required. (Please describe what needs to be updated or link to a PR in the docs

Additional Notes

• The Nix Flake support it's to enable me to test the extension properly on my end.

Get in Touch

Discord: catrielmuller

---

Important

Refactor task execution system to use an iterative approach, enhance memory management, and add Nix flake configuration for development.

• Behavior:
  • Refactor recursivelyMakeClineRequests() in Task.ts from recursive to iterative to prevent stack overflow.
  • Enhance Task.dispose() in Task.ts to remove all event listeners, preventing memory leaks.
  • Add periodic yielding in task processing loops to improve performance.
• Development Environment:
  • Add Nix flake configuration (flake.nix, flake.lock, .envrc) for development environment setup.
• Testing:
  • Add Task.dispose.test.ts to test Task.dispose() method for proper resource cleanup and error handling.

^{This description was created by for a988451. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Consider adding tests to verify that additional cleanup operations (e.g. unsubscribing from task bridge, releasing terminals, closing browsers, and disposing of controllers) are being invoked. This would further ensure that dispose fully prevents resource leaks.

[roomote]

Thank you for your contribution! I've reviewed the changes and found that while the memory leak fix in the dispose() method is excellent, the recursive-to-iterative refactoring needs some adjustments to fully achieve its goal.

[daniel-lxs]

Thank you @catrielmuller!