Safety parser relly on a DB of vulnerabilities with CVE infos. This databases is upgraded/modified every month.
This pb is that our unit tests relly on this changing file.

We need to do one of these options:

1. fix the DB file for unit tests
2. remove completely this feature and wait that the CVE info come from the report (I pushed a pull request upstream to have CVE directly in the JSON rep

We are using pretty outdated deps. These should be upgraded, after all we don't want to be "vulnerable" .

Unrelated: have requirement file separate dev dependencies.