Handle management/info failures gracefully in ProfileService

[krusche]

Summary

ProfileService.getProfileInfo() fetched /management/info with no error handling. When that request fails or returns a non-JSON body (e.g. the backend is unreachable, or the SPA is served standalone), the error propagated uncaught to every subscriber — navbar, footer, page-ribbon, create-simulation-box — and each surfaced in Angular's global ErrorHandler. On the anonymous landing page that's 3 active subscribers ⇒ 3 console errors.

This mirrors the resilience AccountService.identity() already has (catchError(() => of(undefined))): on failure, degrade gracefully to a default ProfileInfo instead of throwing.

.pipe(
  map(...),
  catchError(() => of(new ProfileInfo())), // <- added
  shareReplay(),
)

Context

This surfaced while smoke-testing the Angular 22 PR (#784) by serving the production bundle without a backend: the 3 console errors were all from this missing catchError (the /api/account 401 path was already handled). It is pre-existing and unrelated to the Angular version — in normal deployments /management/info returns JSON, so it never fired. The fix makes the app robust when it doesn't.

Testing

• Production build (pnpm run webapp:prod) ✅
• Served the prod bundle and loaded it in a browser with no backend: 0 console errors (was 3); navbar/footer/landing render unchanged.
• pnpm run lint ✅ · pnpm run prettier:check ✅

🤖 Generated with Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.