ci: update OSV-Scanner to v2.7.0 (#1004)

Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>

Author: vuanhphung

.github/workflows/securityScan.yml

@@ -17,7 +17,7 @@ name: Security Scan
 #
 #   - workflow_dispatch: behaves like the cron run (full reporting).
 #
-# Scanner: OSV-Scanner v2.3.8 (purl-based via OSV.dev; federates GHSA,
+# Scanner: OSV-Scanner v2.7.0 (purl-based via OSV.dev; federates GHSA,
 # NVD, PyPA, RustSec, Go vuln DB). Reads `poetry.lock` natively --
 # no separate SBOM tool needed.
 #
@@ -27,7 +27,7 @@ name: Security Scan
 # justification ("dev-only, not shipped in the wheel").
 #
 # Suppressions live in `osv-scanner.toml` as [[IgnoredVulns]] entries
-# (CVE-id global; OSV-Scanner v2.3.8 doesn't support per-package CVE
+# (CVE-id global; OSV-Scanner v2.7.0 doesn't support per-package CVE
 # scoping). Each entry has a justification comment and an `ignoreUntil`
 # expiry so suppressions re-surface for re-review rather than lingering.
 
@@ -67,7 +67,7 @@ jobs:
         run: |
           set -euo pipefail
           curl -fsSL -o /tmp/osv-scanner \
-            https://github.com/google/osv-scanner/releases/download/v2.3.8/osv-scanner_linux_amd64
+            https://github.com/google/osv-scanner/releases/download/v2.7.0/osv-scanner_linux_amd64
           chmod +x /tmp/osv-scanner
           /tmp/osv-scanner --version
 

osv-scanner.toml

@@ -8,7 +8,7 @@
 # just the artifact we have in mind. The alternative
 # ([[PackageOverrides]] with `vulnerability.ignore = true`) is
 # per-package but blanket-ignores ALL vulnerabilities on that package,
-# which is much worse. OSV-Scanner v2.3.8 does NOT support an
+# which is much worse. OSV-Scanner v2.7.0 does NOT support an
 # intersection ("this CVE on this package only").
 #
 # See google.github.io/osv-scanner/configuration/ for the schema.