fix(detector/vuls2): filter VulnerabilityData by Root ID

[MaineK00n]

If this Pull Request is work in progress, Add a prefix of “[WIP]” in the title.

What did you implement:

Fixes #2246

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

$ curl -s --create-dirs --output results/2025-06-19T05-00-00+0900/rhel_90.json https://raw.githubusercontent.com/vulsio/integration/refs/heads/main/data/results/rhel_90.json

$ cat << EOS > config.toml
version = "v2"

[cveDict]
type = "sqlite3"

[ovalDict]
type = "sqlite3"

[gost]
type = "sqlite3"

[exploit]
type = "sqlite3"

[metasploit]
type = "sqlite3"

[kevuln]
type = "sqlite3"

[cti]
type = "sqlite3"

[vuls2]
repository = "ghcr.io/vulsio/vuls-nightly-db@sha256:788456a519e7f205eb0395410f296535927c8510948937badd190bff3c2156d7"

[default]

[servers]

EOS

$ vuls -v
vuls-v0.32.0-build-20250619_063336_6179618

$ rm vuls.db

$ for i in $(seq 10); do    vuls report --refresh-cve 2025-06-19T05-00-00+0900 &> /dev/null;   jq -r '.scannedCves."CVE-2023-5517".distroAdvisories | length' results/2025-06-19T05-00-00+0900/rhel_90.json; done
1
1
1
1
1
1
1
1
1
1

Checklist:

You don't have to satisfy all of the following.

• Write tests
• Write documentation
• Check that there aren't other open pull requests for the same issue/feature
• Format your source code by make fmt
• Pass the test by make test
• Provide verification config / commands
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES

Reference

[shino]

🥂