Bypassing a group node containing a controlnet cause unexpected behavior

As shown in the video, I also uploaded the corresponding workflow, so you can more easily reproduce the issue, bypassing a group node which contains a controlnet cause this strange behavior.

It doesn't matter if the controlnet group node is complete or not, as it is bypassed anyway, but just if you have doubts, you can complete the controlnet with a preprocessor, etc... it will still cause this strange behavior.

There's a probability this was caused by some recent commit following 2023-12-03 15:25:17, as I have a workflow from that datetime that seems to work, despite having a bypassed grouped controlnet.

https://github.com/comfyanonymous/ComfyUI/assets/1372055/737243ec-0e20-4749-9bc7-7ddf8316676d

[bug.json](https://github.com/comfyanonymous/ComfyUI/files/13579869/bug.json)

Workflow from 2023-12-03 15:25:17 that seems to work, despite having a bypassed grouped controlnet: [working.json](https://github.com/comfyanonymous/ComfyUI/files/13579955/working.json)