fix: clean up Docker resources after executing commands in Breeze

[stegololz]

Fix breeze run leaking a Docker network on every invocation

Each breeze run creates a unique compose project (breeze-run-<uuid>) but never tears it down afterward. The --rm flag on docker compose run removes the container but not the network.

Over time, stale networks accumulate and Docker's IPAM exhausts its default address pool. In my case, it ended with docker Docker allocate an ip identical to my wifi router's IP. This created a bridge interface that captured traffic meant for the real gateway, silently breaking all my IPv4 connectivity.

My implementation wrap the command execution in try/finally and call bring_compose_project_down + remove_docker_networks, matching the existing pattern in testing_commands.py.

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Code (Claude Opus 4.6)

Generated-by: Claude Code (Claude Opus 4.6) following the guidelines

[potiuk]

NICE!

[github-actions]

Backport failed to create: v3-1-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-1-test

You can attempt to backport this manually by running:

cherry_picker 27c11d0 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.