fix(ci): correct Docker context preparation paths

- Fix relative path navigation in Docker preparation script
- Use ../../ to go back to root from artifact subdirectories
- Add proper path handling for Dockerfile copy
- Add verification output to debug binary extraction
- Ensures Linux binaries are properly extracted for Docker build

Author: metaneutrons

.github/workflows/release.yml

@@ -263,21 +263,22 @@ jobs:
           # Extract x64 binary (maps to amd64 in Docker)
           cd docker-artifacts/${{ env.PROJECT_NAME }}-linux-x64
           tar -xzf ${{ env.PROJECT_NAME }}-${{ needs.calculate-version.outputs.version }}-linux-x64.tar.gz
-          mv KnxMonitor ../docker-context/publish-amd64/
+          mv KnxMonitor ../../docker-context/publish-amd64/
           
           # Extract arm64 binary
           cd ../${{ env.PROJECT_NAME }}-linux-arm64
           tar -xzf ${{ env.PROJECT_NAME }}-${{ needs.calculate-version.outputs.version }}-linux-arm64.tar.gz
-          mv KnxMonitor ../docker-context/publish-arm64/
+          mv KnxMonitor ../../docker-context/publish-arm64/
           
           # Copy Dockerfile
-          cp ../Dockerfile ../docker-context/
+          cd ../..
+          cp Dockerfile docker-context/
           
           # Verify binaries
           echo "AMD64 binary:"
-          ls -la ../docker-context/publish-amd64/
+          ls -la docker-context/publish-amd64/
           echo "ARM64 binary:"
-          ls -la ../docker-context/publish-arm64/
+          ls -la docker-context/publish-arm64/
 
       - name: Build and push Docker image
         uses: docker/build-push-action@v5