fix: don't attempt to sort affected events

[G-Rath]

The events should already be sorted since we process version constraints from left to right, and the lower bounds always comes first, and our current sorting implementation both ignores the stability constraint and actually attempts to deduplicate events by their version resulting in some advisories losing their introduced event

[Copilot]

Pull Request Overview

This PR removes the unnecessary sorting of affected version events in the OSV advisory generation process to prevent the inadvertent deduplication of events.

• Removed the sort_affected_versions function and the corresponding sorting call in build_affected_range.
• Now directly uses parse_version_constraint to preserve the original order of events.

Files not reviewed (4)

• advisories/acquia_dam/osv-sa-contrib-2024-025.json: Language not supported
• advisories/diff/osv-sa-contrib-2024-042.json: Language not supported
• advisories/social/osv-sa-contrib-2024-038.json: Language not supported
• advisories/symfony_mailer/osv-sa-contrib-2023-031.json: Language not supported

Comments suppressed due to low confidence (1)

scripts/generate_osv_advisories.py:96

• [nitpick] Ensure there are tests verifying that the ordering of events produced by parse_version_constraint remains consistent with the intended left-to-right constraint processing.

'events': parse_version_constraint(constraint),

[jonholdsworth]

Good catch

[Unifex]

LGTM :)