fix: include purgatory announcements in state event authorization

When processing state events from purgatory, we need to check
authorization against announcements that may still be in purgatory
(not yet promoted to the database).

Previously, process_purgatory_state_events() used fetch_repository_data()
which only queries the database. This caused authorization failures when:
1. Git data arrives
2. Announcement is promoted from purgatory to database
3. State events are processed from purgatory
4. But db_repo_data was fetched BEFORE the announcement promotion

Now uses fetch_repository_data_with_purgatory() to include both
database and purgatory announcements, ensuring authorization works
correctly regardless of promotion timing.

0 files changed, 0 insertions, 0 deletions