MAJOR FIX: Run build directly in Debian container instead of Ubuntu

- Change runner to use debian:trixie container directly
- Remove Docker-in-Docker approach that was causing GPG key conflicts
- Build libfuse directly in Debian environment
- Remove unnecessary Docker cleanup steps
- This should resolve the GPG key verification issues

The previous approach was running Ubuntu runner with Debian container
inside, causing GPG key conflicts between Ubuntu and Debian repositories.

.forgejo/workflows/ci.yml

@@ -12,6 +12,8 @@ jobs:
   build-and-test:
     name: Build and Test
     runs-on: ubuntu-latest
+    container:
+      image: debian:trixie
     
     steps:
     - name: Checkout code
@@ -30,15 +32,10 @@ jobs:
         # Verify files are copied
         ls -la /workspace/particle-os/libfuse/
       
-    - name: Build libfuse in Debian container
+    - name: Build libfuse
       run: |
-        # Run the build directly in Debian container
-        docker run --rm \
-          --add-host=host.docker.internal:host-gateway \
-          -v /workspace/particle-os/libfuse:/workspace \
-          -w /workspace \
-          debian:trixie \
-          bash -c '
+        # Build directly in Debian environment
+        cd /workspace/particle-os/libfuse
         set -e
         
         # Add Debian GPG keys FIRST - this must happen before any apt-get update
@@ -159,7 +156,6 @@ jobs:
         # Verify the library is available
         ldconfig -p | grep libfuse3
         pkg-config --exists fuse3 && echo "fuse3.pc found" || echo "fuse3.pc not found"
-        '
         
     - name: Prepare artifacts
       run: |
@@ -222,9 +218,3 @@ jobs:
         echo "   - Info: artifacts/BUILD_INFO.md"
         echo ""
         
-    - name: Cleanup
-      if: always()
-      run: |
-        # Clean up apt-cacher-ng container
-        docker stop apt-cacher-ng 2>/dev/null || true
-        docker rm apt-cacher-ng 2>/dev/null || true