refactor: Apply cache fixes directly to existing runner configs

- Update all runner configuration files with cache networking fixes:
  - config_docker.yaml
  - config_heavy.yaml
  - config_light.yaml
  - config_security.yaml
- Remove separate config_cache_fixed.yaml file
- Update troubleshooting scripts to use updated configs
- Update documentation to reference existing config files

All runner configs now have:
- Fixed cache host: host.docker.internal
- Fixed cache port: 44029
- Host networking for better container connectivity

This provides a cleaner approach by updating existing configs
instead of maintaining a separate fixed configuration file.

docs/CACHE_TROUBLESHOOTING.md

@@ -31,11 +31,17 @@ This ensures that cache failures don't cause the entire pipeline to fail.
 
 ### 2. Runner Configuration Fixes
 
-Created `runners/config_cache_fixed.yaml` with:
+Updated all existing runner configuration files with:
 - **Fixed Host**: `host.docker.internal` (allows containers to access host)
 - **Fixed Port**: `44029` (instead of random port 0)
 - **Host Network**: Uses host networking for better connectivity
 
+Updated files:
+- `runners/config_docker.yaml`
+- `runners/config_heavy.yaml`
+- `runners/config_light.yaml`
+- `runners/config_security.yaml`
+
 ### 3. Troubleshooting Tools
 
 Created diagnostic scripts:
@@ -46,16 +52,22 @@ These scripts help diagnose and fix cache issues.
 
 ## How to Apply the Fixes
 
-### Option 1: Use the Fixed Configuration
+### Option 1: Use the Updated Configuration
 
 1. Stop your current runner:
    ```bash
    pkill -f act_runner
    ```
 
-2. Start with the fixed configuration:
+2. Start with an updated configuration:
    ```bash
-   ./act_runner daemon --config config_cache_fixed.yaml
+   ./act_runner daemon --config config_docker.yaml
+   # or
+   ./act_runner daemon --config config_heavy.yaml
+   # or
+   ./act_runner daemon --config config_light.yaml
+   # or
+   ./act_runner daemon --config config_security.yaml
    ```
 
 ### Option 2: Run the Troubleshooting Script