Reap orphaned Azure provisioning tunnels

[mkultraWasHere]

Azure provisioning tunnels now clean up even when the DreadGOAD CLI is hard-killed by the console.

Added

• A hidden parent-lifetime watchdog supervises the Azure provisioning tunnel process group.

Fixed

• az network bastion tunnel processes no longer survive abrupt CLI termination.
• Tunnel descendants are reaped even when the original process-group leader has already exited.

Notes

• The user-invoked dreadgoad bastion tunnel command remains on its existing interactive lifecycle path.

[Copilot]

Pull request overview

This PR hardens Azure provisioning tunnels by introducing a dedicated watchdog subprocess that can terminate and reap the entire az network bastion tunnel process group even if the main DreadGOAD CLI process is abruptly killed, preventing orphaned tunnel processes from persisting.

Changes:

• Adds a hidden __bastion-watchdog Cobra command that supervises a child command until a parent-lifetime FD closes.
• Refactors provisioning tunnel startup/teardown to launch and coordinate with the watchdog via a pipe-based liveness signal.
• Expands regression tests to cover parent-death cleanup and “leader exited but descendant still alive” process-group tracking.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
cli/internal/azure/provision_tunnel.go	Introduces watchdog-backed bastion tunnel lifecycle management and process-group reaping logic.
cli/internal/azure/provision_tunnel_test.go	Adds/updates tests validating watchdog cleanup behavior and process-group termination semantics.
cli/cmd/bastion_watchdog.go	Adds the hidden __bastion-watchdog CLI entry point used by provisioning tunnels.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

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