fix(desktop): resolve project clone fallback origin

[sandeepgoenka]

Summary

• resolve the repository clone URL fallback asynchronously from the relay origin when a legacy project announcement has no clone tag
• preserve the cached fast path while allowing Projects to load correctly before the relay-origin cache is populated
• keep snapshot queries safely disabled when relay-origin lookup temporarily fails

Root cause

Projects mapped repository announcements synchronously from a relay-origin cache. If the Projects screen loaded before that cache was populated, a legacy announcement such as sandeep-pkm was permanently mapped without a clone URL. The commit snapshot query therefore remained disabled even though the Git repository and its full history were present on the Buzz Git server.

User impact

Legacy Buzz projects without an explicit clone tag can now display their repository contents after startup without requiring users to recreate, re-upload, or manually maintain the repository.

Validation

• 3,909 Desktop unit tests passed
• TypeScript typecheck passed
• formatting/static checks passed
• file-size checks passed
• regression coverage added for the startup race, cached fast path, and temporary relay-origin lookup failure

Commit: 40c7c163f7cc15d16849dc5ee0a886141ea1969c