fix: Update node tar resolution (BED-9461)

[dcairnsspecterops]

Description

This PR updates the resolution for node-tar due to a vulnerability.

Motivation and Context

Resolves: BED-9461

Why is this change required? What problem does it solve?

How Has This Been Tested?

Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc.

Screenshots (optional):

Types of changes

• Chore (a change that does not modify the application functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Database Migrations

Checklist:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Issues and Pull Requests README #672
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments (GoDocs / JSDocs)
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed

Summary by CodeRabbit

• Chores
  • Updated the bundled tar package to version 7.5.22 for improved maintenance and compatibility.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 2965ef69-a5c9-4f8f-b312-44dcb10eca41

📥 Commits

Reviewing files that changed from the base of the PR and between 9be60d8 and d8b9e1b.

⛔ Files ignored due to path filters (2)

• .yarn/cache/tar-npm-7.5.22-4f603e5fa8-129606384b.zip is excluded by !**/.yarn/**, !**/*.zip
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• package.json

Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

---

📝 Walkthrough

Walkthrough

The root package resolution for tar changes from 7.5.19 to 7.5.22. No exported or public entities change.

Changes

Tar resolution update

Layer / File(s)	Summary
Update tar package resolution package.json	The root package resolution updates tar from 7.5.19 to 7.5.22.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to d8b9e

This PR makes a localized node-tar dependency resolution update; no actionable merge-blocking risk remains based on the supplied evidence.

Suggested reviewers: thenando, urangel

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description states the change and motivation, but it lacks testing details and leaves the change type and checklist incomplete.	Add the testing environment and test results, select the applicable change type, and complete or update the checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the node-tar resolution update and includes the associated ticket.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-node-tar-resolution

---

_{Comment @coderabbitai help to get the list of available commands.}

[urangel]

ty!