chore: Update SonarQube project configuration for CI workflows

### Summary of Changes
- Changed SonarQube project keys and names for all services to follow a consistent naming convention.
- Replaced `sonar-scanner` with `@sonar/scan` in the frontend and other workflows for improved compatibility.
- Simplified SonarQube analysis commands by removing unnecessary parameters and ensuring each service reports to its dedicated project.

### Expected Results
- Enhanced clarity and maintainability of CI configurations.
- Improved isolation of quality metrics for each service in SonarQube.
- Streamlined integration process for better reporting and analysis.

.gitea/workflows/frontend.yml

@@ -80,20 +80,14 @@ jobs:
       run: |
         echo "Sending Frontend results to SonarQube..."
         # Install SonarQube Scanner for Node.js
-        npm install -g sonar-scanner
+        npm install -g @sonar/scan
         
         # Run SonarQube analysis
         sonar-scanner \
           -Dsonar.host.url=${{ secrets.SONAR_HOST_URL }} \
           -Dsonar.login=${{ secrets.SONAR_TOKEN }} \
-          -Dsonar.projectKey=labFusion \
-          -Dsonar.projectName="LabFusion" \
-          -Dsonar.projectVersion=1.0.0 \
-          -Dsonar.modules=frontend \
-          -Dsonar.sources=src \
-          -Dsonar.tests=src \
-          -Dsonar.javascript.lcov.reportPaths=coverage/lcov.info \
-          -Dsonar.testExecutionReportPaths=test-results.xml
+          -Dsonar.projectKey=labfusion-frontend \
+          -Dsonar.projectName=LabFusion Frontend
         
     - name: Test results summary
       if: always()