Duplicate range found for repository in NVD affected ranges

Investigate this in combine-to-osv in pantheon. Better logs are needed to know where this is coming from.

Start by locating the combine-to-osv entry point and its Pantheon deployment or logs. Reproduce or trace handling of the duplicate repository range, then identify where the duplicate is introduced. Done means the relevant path emits enough context to determine the source of the duplicate range.

Written by the indexing model from the issue text.