fix: disable Docker build cache to force database update

- Added no-cache: true to docker/build-push-action
- Previous builds were aggressively caching the old database from 13:18
- This forces a complete rebuild including the new database with trigger fixes
- Build will take longer (5-10min vs 26sec) but ensures correct database

The cache was so aggressive that even Dockerfile changes didn't invalidate it.
This nuclear option ensures the trigger detection fixes for webhook, cron,
interval, and emailReadImap nodes are finally included in the Docker image.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.github/workflows/docker-build.yml

@@ -63,19 +63,11 @@ jobs:
         uses: docker/build-push-action@v5
         with:
           context: .
+          no-cache: true
           platforms: linux/amd64,linux/arm64
           push: ${{ github.event_name != 'pull_request' }}
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
-          # Use both GHA and registry cache for better performance
-          cache-from: |
-            type=gha
-            type=registry,ref=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:buildcache
-          cache-to: |
-            type=gha,mode=max
-            type=registry,ref=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:buildcache,mode=max
-          build-args: |
-            BUILDKIT_INLINE_CACHE=1
           provenance: false
 
   # Nginx build commented out until Phase 2