micromamba run should pass signals to child

[jonashaag]

I need to double check this but it seems like signals are not (always?) passed to the child. To reproduce, run micromamba run bash and press Ctrl+C, it will stop the child (but only on Windows?).

[ken-lauer]

I ran into this bug this week, where the subprocesses of micromamba run were somehow getting orphaned rather than killed. I was rather surprised to find micromamba run not able to forward signals to be the cause.

For context, this was using micromamba run to spawn conda environment-based IPython kernels for JupyterHub - this isn't something that's officially supported, but rather something I'm testing out. For now to avoid this issue, it seems like eval "$(micromamba shell hook -s bash)" && micromamba activate /path/to/env && exec python -m ipykernel_launcher ... may be my best option, however clunky it may be.