ci: add npmscan dependency security check

[salemalem]

What does this PR do?

Integrates npmscan-action as a non-blocking supply-chain security check on Pull Requests.

npmscan checks incoming PRs for:

• Lockfile overrides that could pull in malicious transitive dependencies
• Unexpected new postinstall scripts
• Tarball swaps and checksum mismatches

Why?

Supply-chain attacks (like the recent ChainDrop and malicious axios typosquats) often sneak in via lockfile updates in otherwise benign PRs. This check helps reviewers spot those anomalies automatically.

Configuration Notes

• Non-blocking: Configured with mode: warn and fail-on-error: false. It will only post a warning annotation if an issue is found and will never fail the CI build, ensuring it doesn't disrupt your workflow.
• Immutable Action: The action is pinned to a specific commit SHA (de14168f65640a4ed1f0e82ad3ad8c80483d360d) rather than a floating tag, following security best practices.

[meta-cla]

Hi @salemalem!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!