feat: support devDependencies on package.json parser

[arthurdenner]

Fixes #173.

Screenshot

As --dev is the trigger for scanning devDependencies, I've approached the issue like this:

1. Pass the additional CLI parameters to the package.json parser;
2. Look for the --dev string inside the parameters (if provided)
3. Check if there are devDependencies in the package.json
4. If 2 and 3 are true, parse the devDependencies as the dependencies

Let me know if you have suggestions for changes or if I have approached the issue incorrectly.

[CLAassistant]

All committers have signed the CLA.

[michelkaporin]

Hi @arthurdenner! Thank you for your PR. Since we don't often receive product functionality contributions we need to run it by team and I'll get back to you right afterwards. The code looks good so far ✔️ Apologise for the delay.

[michelkaporin]

@arthurdenner Apologise for taking it too long. We iterated with the team on how should we approach feature contributions. For instance, given we have other IDE plugins, we're trying to ensure we're consistent with our product functionality across all of them. That means if feature lands in VS Code extension, it should be also added to IntelliJ plugin, Visual Studio extension, etc.

All in all we're ready to accept your PR, please resolve the conflicts and let me know. Thank you!

[arthurdenner]

@michelkaporin, I've updated the PR after solving the conflicts.
Let me know if there's any change to do! ✌🏽

[michelkaporin]

Great! Thank you for your contribution 👏

Update: Just realised your commits should be signed before we merge in, please sign them 🙏

[arthurdenner]

@michelkaporin, done! Apologies for the delay.