fix(ci): docker network prune does not support -a

[renecannao]

Problem

The docker-state nuke from PR #6049 fails on the self-hosted runners:

Usage:  docker network prune [OPTIONS]
##[error]Process completed with exit code 125.

Root cause

docker network prune only accepts -f/--force and --filter — the -a/--all flag is not supported (unlike docker volume prune, which has -a). Passing -af is an invalid flag combination, so the command aborts with a usage error.

Fix

Use docker network prune -f in both the preflight and post-job nuke steps. Network prune already removes all unused networks, so no -a is needed.

---

Summary by cubic

Fixes CI cleanup by replacing docker network prune -af with docker network prune -f in .github/workflows/ci-builds.yml preflight and post-job nuke steps. Previously, -a was invalid for network prune and caused exit 125 on self-hosted runners; now the command runs non-interactively and prunes all unused networks, preventing cleanup failures without changing volume pruning.

^{Written for commit 04eb487. Summary will update on new commits.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud