Fix: Use single concurrency group to prevent deployment conflicts

Changed from per-branch concurrency groups to a single global group
for all gh-pages deployments. This prevents main and develop branch
workflows from running simultaneously and conflicting when pushing
to the gh-pages branch.

Changes:
- Concurrency group changed to single 'gh-pages-deployment' group
- This makes all deployments queue up instead of running in parallel
- cancel-in-progress: false ensures workflows complete without cancellation

Fixes deployment race conditions and skipped steps.

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

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

Author: hackall360

.github/workflows/deploy.yml

@@ -17,9 +17,10 @@ permissions:
   issues: write
   pull-requests: write
 
-# Ensure only one deployment runs at a time per branch
+# Ensure only one deployment runs at a time across ALL branches
+# This prevents main and develop from conflicting when pushing to gh-pages
 concurrency:
-  group: "pages-${{ github.ref_name }}"
+  group: "gh-pages-deployment"
   cancel-in-progress: false
 
 jobs: