Fix inconsistencies for `affected_range`
Based on the work done in gitlab-org/gitlab#14630 (closed), we could reveal some inconsistencies in the affected_range field; we revealed them by executing the vrange tools and checked the output for parsing errors, and fixed the affected_ranges in the corresponding .yml files.
related issue: https://gitlab.com/gitlab-org/security-products/advisory-db-curation-tools/issues/2#note_206690146
Edited by 🤖 GitLab Bot 🤖