chore: restore npm lockfile integrity metadata

[iamanaws]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Restores missing resolved and integrity metadata in package-lock.json.

The lockfile was updated with npm-lockfile-fix to work around an npm issue where npm install can remove registry metadata from lockfile entries: npm/cli#6301

This improves reproducibility for package managers and downstream consumers that rely on complete lockfile metadata.

Where should the reviewer start?

Review package-lock.json. This PR is lockfile-only.

How should this be manually tested?

Run:

npm ci

[CLAassistant]

All committers have signed the CLA.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.