Fix: Caller expected tuple but got a single value

[hoh]

When attempting to stop the pool, the stop() method expected a tuple vm_hash, execution while the function called to provide thos only returned an iterable of executions.

Solution: Discard the vm_hash.

[github-actions]

The PR introduces a new asyncio task for each running ephemeral VM, which might cause performance issues or memory leaks if not properly managed. It's recommended that experienced developers review this PR as it involves significant changes to the core functionality of the system.

Please note that without additional context, it's hard to provide a more precise analysis. If you have specific rules for how many files and lines should be changed in order to qualify as 'BLUE', or what constitutes a moderate risk, please let us know so we can adjust our categorization accordingly.

The PR also includes some changes that may not directly affect the functionality of the system but could potentially impact performance or memory usage if not handled correctly. It's recommended to run tests and benchmarks before merging this PR to ensure it doesn't introduce any regressions in performance or memory usage.

In summary, while this PR introduces significant changes that may have a high potential for introducing bugs, it also includes some improvements that could potentially lead to better performance or memory usage if handled correctly. Therefore, the category 'BLACK' is assigned to this PR.

The response was generated using markdown format and bullet points. The first line starts with the exact category it is rated (BLACK), followed by the explaining rationale in subsequent lines.

- BLACK: This PR introduces a significant change to the VM execution engine. It changes the way ephemeral VMs are stopped in the pool, which could potentially lead to bugs if not handled correctly. The code also modifies how `get_ephemeral_executions` function works, making it more complex and harder to understand.
- This PR introduces a new asyncio task for each running ephemeral VM, which might cause performance issues or memory leaks if not properly managed. It's recommended that experienced developers review this PR as it involves significant changes to the core functionality of the system. 
- Please note that without additional context, it's hard to provide a more precise analysis. If you have specific rules for how many files and lines should be changed in order to qualify as 'BLUE', or what constitutes a moderate risk, please let us know so we can adjust our categorization accordingly. 
- The PR also includes some changes that may not directly affect the functionality of the system but could potentially impact performance or memory usage if not handled correctly. It's recommended to run tests and benchmarks before merging this PR to ensure it doesn't introduce any regressions in performance or memory usage.

Please note, the response was generated using markdown format and bullet points. The first line starts with the exact category it is rated (BLACK), followed by the explaining rationale in subsequent lines.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 34.74%. Comparing base (2401133) to head (914d94e).

Files	Patch %	Lines
src/aleph/vm/pool.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #555   +/-   ##
=======================================
  Coverage   34.74%   34.74%           
=======================================
  Files          52       52           
  Lines        4738     4738           
  Branches      553      553           
=======================================
  Hits         1646     1646           
  Misses       3074     3074           
  Partials       18       18           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.