Update deprecated syft packages command to syft scan

Makefile

@@ -219,10 +219,11 @@ test-docs-and-schema:
 
 # INTERNAL: used to test for new CVEs that may have been introduced
 test-cves:
-	go run main.go tools sbom packages . -o json --exclude './docs-website' --exclude './examples' | grype --fail-on low
+	go run main.go tools sbom scan . -o json --exclude './docs-website' --exclude './examples' | grype --fail-on low
 
 cve-report: ## Create a CVE report for the current project (must `brew install grype` first)
-	go run main.go tools sbom packages . -o json --exclude './docs-website' --exclude './examples' | grype -o template -t hack/.templates/grype.tmpl > build/zarf-known-cves.csv
+	@test -d ./build || mkdir ./build
+	go run main.go tools sbom scan . -o json --exclude './docs-website' --exclude './examples' | grype -o template -t hack/.templates/grype.tmpl > build/zarf-known-cves.csv
 
 lint-go: ## Run revive to lint the go code (must `brew install revive` first)
 	revive -config revive.toml -exclude src/cmd/viper.go -formatter stylish ./src/...

docs/3-create-a-zarf-package/6-package-sboms.md

@@ -30,7 +30,7 @@ Given the Syft CLI is vendored into Zarf you can run these commands with the Zar
 
 ```bash
 # Syft is vendored as `zarf tools sbom`
-$ zarf tools sbom packages file:path/to/yourproject/file -o json > my-sbom.json
+$ zarf tools sbom scan file:path/to/yourproject/file -o json > my-sbom.json
 ```
 
 :::