Allow for filtering on major/minor updates when using npm as a source for (outdated) dependencies

[Sebastiaan127001]

Describe the solution you'd like
When using npm as a source for measuring (outdated) dependencies, the results (updatable deps) can easily accumulate far above 1000 deps. This is unmanageable for a team. npm does not supply a method for generating an output file with only major and minor updates. It would therefore be useful it Quality-time provides this feature.

situation 1 (should not be shown in the JSON output file)

{

  **"current": "3.25.76",

  "wanted": "3.25.76",

  "latest": "3.25.77",**

  "dependent": "@modelcontextprotocol/sdk",

  "location": "/src/node_modules/zod",

  "type": "dependencies",

  "homepage": "https://zod.dev",

  "dependedByLocation": "node_modules/@modelcontextprotocol/sdk"

},

situation 2 (SHOULD BE displayed in the JSON output file)

{

  **"current": "3.25.76",

  "wanted": "3.25.76",

  "latest": "4.2.1",**

  "dependent": "@modelcontextprotocol/sdk",

  "location": "/src/node_modules/zod",

  "type": "dependencies",

  "homepage": "https://zod.dev",

  "dependedByLocation": "node_modules/@modelcontextprotocol/sdk"

}, 

[Sebastiaan127001]

When using OWASP dependency-check as a source for the metric 'dependencies' the user DOES have the possibility to filter on path (see below). We could consider merging the metrics 'outdated dependencies' and 'dependencies' (just like we did/planned with other metrics like branches/jobs/test cases).