[claude] One unreachable Lexbox server hides remote projects from all servers

CombinedProjectsService.RemoteProjects (CombinedProjectsService.cs:54) awaits ServerProjects(...) per server in a loop with no per-server error handling. GetLexboxProjects, GetLexboxUser or UpdateProjectServerInfo throwing for one server propagates out of the whole method, so results already gathered from healthy servers are discarded.

With two servers configured and one unreachable, the user sees no remote projects at all rather than the reachable server's list.

Fix: catch per server, return what succeeded, and mark the failed server so the UI can show it as unavailable rather than empty.

Note the Platform.Bible extension currently masks this: lexicon.remoteProjects returns undefined on error and the web view keeps the last-known list (platform.bible-extension/src/web-views/select-lexicon.web-view.tsx:62-67), so on first open the section is simply absent.

Pre-existing; surfaced during review of #2585.

Start at CombinedProjectsService.cs:54 and trace ServerProjects, including GetLexboxProjects, GetLexboxUser, and UpdateProjectServerInfo. Compare the error behavior with platform.bible-extension/src/web-views/select-lexicon.web-view.tsx:62-67; done means healthy servers' projects remain available while a failed server is marked unavailable rather than treated as empty.