chr: use SONAR_PROJECT_KEY and SONAR_ORGANIZATION env vars in build

The new repos will have these vars set. For now the build falls back to the
previous values, if the variables are not set.

Author: dblankevia

.github/workflows/test.yml

@@ -24,7 +24,19 @@ jobs:
         cmd: install # will run `yarn install` command
     - name: Run npm test:ci
       run: CHROMIUM_BIN=$(which chrome) npm run test:ci # will run `test:ci` command
-    - uses: SonarSource/sonarcloud-github-action@master
+    - name: Run SonarCloud with organzation and project key from environment
+      uses: SonarSource/sonarcloud-github-action@master
+      if: ${{ vars.SONAR_ORGANIZATION != '' && vars.SONAR_PROJECT_KEY != '' }}
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Needed to get PR information, if any
+        SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+      with:
+        args: >
+          -Dsonar.organization=${{ vars.SONAR_ORGANIZATION }}
+          -Dsonar.projectKey=${{ vars.SONAR_PROJECT_KEY }}
+    - name: Run SonarCloud with hardcoded organization and project key
+      uses: SonarSource/sonarcloud-github-action@master # Fallback for the catenax-ng/product-traceability-foss-frontend
+      if: ${{ vars.SONAR_ORGANIZATION == '' || vars.SONAR_PROJECT_KEY == '' }}
       env:
         GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Needed to get PR information, if any
         SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}