fix(ci): scope sonarqube workflow to main/develop only to eliminate PR race condition

When sonarqube.yml ran on push to copilot/** branches, it competed with the
pull_request trigger. Branch-mode analysis (push) and PR-mode analysis
(pull_request) both uploaded to SonarCloud; whichever arrived last set the
check status. Branch mode applies a coverage gate (≥80%); PR mode does not.
This caused #347 and #357 to fail intermittently depending on which analysis
completed last.

Fix: only run sonar analysis on pushes to main/develop (branch tracking) and
on pull_request events targeting main/develop (PR analysis in PR mode). PRs
from copilot/** will still get sonar via the pull_request event.

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

Author: bedaHovorka

.github/workflows/sonarqube.yml

@@ -2,9 +2,9 @@ name: SonarQube Analysis
 
 on:
   push:
-    branches: [ main, develop, 'feature/**', 'feat/**', 'fix/**', 'copilot/**', 'claude/**' ]
+    branches: [ main, develop ]
   pull_request:
-    branches: [ main, develop, 'feature/**', 'feat/**', 'fix/**', 'copilot/**', 'claude/**' ]
+    branches: [ main, develop ]
   workflow_dispatch:  # Allow manual trigger
 
 permissions: