Fix SonarQube error and refine trigger conditions

The SonarQube weekly analysis workflow was failing due to a missing
`compile_commands.json` file. This occurs because the build-wrapper
output directory was previously referenced with an incorrect path
containing an unintended quotation mark, causing the CFamily plugin
to abort with a NoSuchFileException.

This change fixes the failure by aligning the workflow with
SonarCloud recommended usage.

Additionally, this commit updates the workflow triggers:
- `push` now explicitly targets the `main` branch;
- `pull_request` now includes path-level filters so that the workflow
  runs whenever the workflow file itself is modified.

Author: tuhaihe

.github/workflows/sonarqube.yml

@@ -32,6 +32,7 @@
 # Triggers:
 # - Weekly schedule
 # - optional manual dispatch.
+# - Changes on sonarqube.yml file
 #
 # Notes:
 # - SONARCLOUD_TOKEN secret is provided by the ASF Infra team
@@ -42,6 +43,14 @@ on:
   schedule:
   - cron: "0 0 * * 1"
   workflow_dispatch:
+  push:
+    branches:
+      - main
+    paths:
+      - '.github/workflows/sonarqube.yml'
+  pull_request:
+    paths:
+      - '.github/workflows/sonarqube.yml'
 
 permissions:
   contents: read
@@ -117,4 +126,4 @@ jobs:
         SONAR_TOKEN: ${{ secrets.SONARCLOUD_TOKEN }}
       with:
         args: >
-          --define sonar.cfamily.compile-commands="${{ env.BUILD_WRAPPER_OUT_DIR }}/compile_commands.json"
+          --define "sonar.cfamily.compile-commands=${{ env.BUILD_WRAPPER_OUT_DIR }}/compile_commands.json"