Broaden NPM detection for VS Code extensions

[pjcollins]

Context: #1348
Context: microsoft/vscode#295040

Commit a209393 added logic to ignore NPM dependencies declared in a
package.json file if it belonged to a VS Code extension. This was done
to ignore warnings for out of date package versions that are built
directly into VS Code, however it also limits detection capabilities for
all VS Code extension files.

A change was made to bump the built in package versions in VS Code in
commit microsoft/vscode@e987c52
which should allow us to revert this change and restore broader NPM
detection for VS Code extensions.

[pjcollins]

FYI @rzhao271 and @dtivel

[Copilot]

Pull request overview

This PR restores full npm package.json detection for VS Code extensions by removing the special-case logic that previously skipped packages declaring a vscode engine, aligning behavior with the updated VS Code built-in package versions.

Changes:

• Remove VS Code extension skip logic from NpmComponentDetector (no longer ignores engines.vscode).
• Bump NpmComponentDetector version to reflect the behavior change.
• Update unit tests to assert that VS Code engine packages are detected (including the malformed engines-as-array case).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/Microsoft.ComponentDetection.Detectors/npm/NpmComponentDetector.cs	Removes VS Code engine-based skip behavior and increments detector version.
test/Microsoft.ComponentDetection.Detectors.Tests/NpmDetectorTests.cs	Updates tests to expect detection for packages with engines.vscode (object and array cases).