fix: break circular deadlock in sync loop by including purgatory in URL lookup

The sync loop calls fetch_repository_data() to get clone URLs so it knows
where to fetch git data from. Previously this only queried the database,
which means an announcement still in purgatory (no git data yet) would
return no clone URLs, so the sync loop could never fetch the git data
needed to promote the announcement - a circular deadlock.

Fix by switching to fetch_repository_data_with_purgatory() which combines
database announcements with purgatory announcements. Update the trait
method's doc comment to document this behaviour.

The mock implementation in tests is unaffected since it returns
pre-configured data rather than delegating to either function.

0 files changed, 0 insertions, 0 deletions