🤖 ci: fix Docker Compose exec issue by using run instead

- Replace docker compose exec with docker compose run --rm

- Remove unnecessary container startup step

- Fixes 409 TCP upgrade error in CI workflow

- Maintains same functionality with better isolation

.gitea/workflows/ci-cd.yaml

@@ -166,19 +166,11 @@ jobs:
       - name: Export DEPS_HASH for Docker Compose
         run: echo "DEPS_HASH=${{ needs.build-cache.outputs.deps_hash }}" >> $GITHUB_ENV
 
-      - name: Start build cache container with Docker Compose
-        run: |
-          echo "Starting build cache container..."
-          DEPS_HASH="${{ needs.build-cache.outputs.deps_hash }}"
-          echo "DEPS_HASH=$DEPS_HASH"
-          export DEPS_HASH
-          docker compose -f docker-compose.build.yml up -d build-cache
-
       - name: Generate Swagger Docs using Docker Compose
-        run: docker compose -f docker-compose.build.yml exec -w /workspace/pkg/server build-cache sh -c "go generate"
+        run: docker compose -f docker-compose.build.yml run --rm -w /workspace/pkg/server build-cache sh -c "go generate"
 
       - name: Build all packages using Docker Compose
-        run: docker compose -f docker-compose.build.yml exec -w /workspace build-cache sh -c "go build ./..."
+        run: docker compose -f docker-compose.build.yml run --rm -w /workspace build-cache sh -c "go build ./..."
     
 
       - name: Wait for PostgreSQL to be ready