chore(pkgd-action): update action.yml action name and test assertions

[divisionseven]

Summary

Renames the GitHub Action's display name in action.yml from "Package Defender Security Audit" to "PKG-Defender Security Audit" for brand consistency, and updates the corresponding test assertion in github-action/tests/action.test.js.

---

Type of Change

• 🧹 Chore (brand consistency, naming)

---

Motivation and Context

The action's Marketplace display name was "Package Defender Security Audit" but the project's official name is PKG-Defender. This inconsistency meant users browsing the GitHub Marketplace would see the wrong brand name. This change aligns the action's name with the rest of the project's branding.

---

Implementation Notes

Two files changed, two insertions, two deletions:

File	Line	Change
github-action/action.yml	1	name: 'Package Defender Security Audit' → name: 'PKG-Defender Security Audit'
github-action/tests/action.test.js	41	Expected name updated to match

There are no functional changes — the action's inputs, outputs, runtime behavior, and Marketplace metadata are entirely unaffected.

---

Testing

• I have added tests that cover the changes in this PR
• All existing tests pass locally (pytest --cov-fail-under=90)
• I have run the e2e gate test locally (pytest tests/integration/test_smoke_e2e.py --tb=short -q)
• I have tested this manually (describe what you did below)

Manual testing performed:

• Verified the updated name field in action.yml reads "PKG-Defender Security Audit"
• Verified the test assertion in action.test.js matches the new name

---

Checklist

• My code follows the project's style guidelines (passes ruff check . and ruff format --check .)
• My code passes type checking (mypy .)
• My changes maintain or improve code coverage (pytest --cov-fail-under=90)
• My CLI changes use the correct exit codes defined in docs/reference/exit-codes.md
• I have updated documentation as needed (README, docstrings, CHANGELOG)
• I have updated CHANGELOG.md with a brief entry under [Unreleased]
• My changes do not introduce new dependencies without discussion
• Any new dependencies are pinned appropriately in pyproject.toml
• I am aware that the dependency review workflow (.github/workflows/dependency-review.yml) runs automatically on PRs
• I have reviewed my own diff before requesting review

---

Screenshots / Output

N/A

---

Breaking Changes

None.

---

Related Issues / PRs

None.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!