Update vulnerabilities database script

[oleole39]

Here is the script that generated this file: YunoHost/apps#3274

It comes together with a README.md which gives most of the info that might be required.

It is meant to be run regularly, at minimum every 119 days not to risk missing some entries (cf. NIST NVD API limitation of 120 days lookup span in call_nist()) . Several API calls could be made instead of one to have a larger period, but it should be unnecessary as anyway running the script much more often would be better from the security point of view.

Note in particular that:

• --pr feature hasn't been tested yet. It needs a github token.
• NIST_API_KEY could be set as env variable via a Github repository secret to speed up the script execution.

This scripts makes use of appslib/get_apps_repo.py and appslib/utils.py, add this PR adds a security.toml-related function to the latter.

PS: You will run into TOML formatting issue you don't want to cope with if you try to run it with the original security.toml template. If you want to run the script against that version, you'd better use this version with no starting space/tabs instead. If you try the script on a TOML file generated by a previous run of the script, there will be no issue.

[oleole39]

Also, the log warns when an app may have a "CPE" although not declared in the manifest:
https://paste.yunohost.org/adahojukeb.log

It does so by looking by using the app_id as keyword for search at EUVD. If there is a match there although no CPE is defined in the manifest (whether because it didn't exist at the time of initial packaging, or because it was forgotten), it can suggest there now one available. But it can also be a false positive, given that search on EUVD is not strict (or at least it is not documented for now I guess) - i.e. searching for element also returns results for Photoshop Elements and Elementor...