Global NVD Vulnerability Data

[digitalcoyote]

What is the Feature? Please describe.
There are multipel issues with the NVD source currently including #70 . I intend to move the vulnerability data binary to a the AppData Special folder (This maps to different folders on Linux/Mac/Windows).

Use Case
Global NVD Data means less chance of failig an update, and the abiltiy to more easily manually update the data..

Describe alternatives you've considered
No alternatives considered

Additional context
This replaces an option that previously never worked that would allow the user to point multiple configurations to a single NVD file.

[digitalcoyote]

There are some issues with the current NVD Data format. It's taking significant memory to use. I think it would be better to use something like SqlLite or any SQL cache (perhaps using EntityFramework so anything it supports can be configured via connection string. I would like to still have the ability to use the old MessagePack data as well, but I'm seeing it use too much memory locally and my gut says it's because it's pulling the entire dictionary into memory and in many scenarios this could be offloaded to a DB as a Service or perhaps more efficiently using sqlLite.

Any PR's towards this are welcome. Just let me know the plan before you get started on it. :)

[digitalcoyote]

Minor step in fixing one of the issues with the vulnerability source will be incomind soon. The file handles was being opened outside of the retry soanother program having a lock o nthe file was failing it instead of allowing it to retry