ci: inherit secrets in CI and release workflows

- Added `secrets: inherit` to the CI job in `ci.yml` to ensure secrets are available during the CI process.
- Added `secrets: inherit` to the verify_release job in `release.yml` for consistent access to secrets.
- Updated the condition for publishing coverage in `shared-ci.yml` to check if the coverage token is not empty, enhancing security.

Author: niteshpurohit

.github/workflows/ci.yml

@@ -17,5 +17,6 @@ jobs:
     permissions:
       contents: read
     uses: ./.github/workflows/shared-ci.yml
+    secrets: inherit
     with:
       upload_coverage: true

.github/workflows/release.yml

@@ -22,6 +22,7 @@ jobs:
     permissions:
       contents: read
     uses: ./.github/workflows/shared-ci.yml
+    secrets: inherit
     with:
       upload_coverage: false
 

.github/workflows/shared-ci.yml

@@ -136,7 +136,7 @@ jobs:
         working-directory: ${{ env.APP_DIR }}
         run: bin/rspec --format documentation --color --profile
       - name: Publish coverage to Qlty
-        if: inputs.upload_coverage && matrix.ruby_version == '3.4'
+        if: inputs.upload_coverage && matrix.ruby_version == '3.4' && secrets.QLTY_COVERAGE_TOKEN != ''
         uses: qltysh/qlty-action/coverage@v2
         with:
           token: ${{ secrets.QLTY_COVERAGE_TOKEN }}