chore(deps): update ferrlabs/.github digest to efe7f97

[ferrlabs-renovate]

This PR contains the following updates:

Package	Type	Update	Change
FerrLabs/.github (changelog)	workflow	digest	9de9605 → efe7f97

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[ferrfleet]

Digest bump 9de9605 → efe7f97 for FerrLabs/.github spans a single upstream commit (FerrLabs/.github#340).

What changed: only reusable-sonarqube-scan.yml has real content changes — it drops the PR-sandbox project and diff-comment logic and now hard-skips the analysis job on pull_request events (if: github.event_name != 'pull_request'), same pattern added to reusable-ci-{astro,go,node,rust}.yml (LFSX doesn't call those). reusable-docker-build.yml, reusable-ferrflow-release.yml, and reusable-security-scan.yml — used by docker.yml, release.yml, security-scan.yml here — are untouched by this commit, so those three files' diffs are digest-only with zero behavior change.

What breaks here: nothing. .github/workflows/sonarqube.yml calls the changed reusable, so on future PRs the scan job's sonarqube step will just show as skipped instead of posting the Sonar delta comment it used to (no <repo>-pr sandbox project analysis anymore). Push-to-main analysis is unaffected. Nit: the caller's pull-requests: write permission and its comment about needing it for "the reusable comments the issue delta on pull requests" (sonarqube.yml:98-99) are now stale, since that step no longer runs — harmless to leave, but worth pruning next time that file is touched.

CI: nothing has failed as of this review; most jobs were still queued/in-progress at check time.