feat: enhance error handling in git-push and repo services

[dcoric]

Summary

This PR fixes both:

• Fixes Poor error messaging in the admin UI when the user is not logged in #1392
• Fixes Improve UI error handling and API error codes #1188

Improve error handling and test coverage for UI services

This PR refactors error handling across the UI service layer and adds comprehensive test coverage. Error handling is now consistent, type-safe, and properly tested.

What's changed

Error handling improvements:

• Added src/ui/services/errors.ts with reusable error utilities (getServiceError, errorResult, successResult)
• Refactored git-push.ts and repo.ts services to use the new error handling utilities
• Updated UI views (PushDetails.tsx, RepoDetails.tsx, etc.) to properly handle and display error states
• All service functions now return consistent ServiceResult<T> objects with success/failure states

Test coverage (14 → 79 tests):

• test/ui/errors.test.ts - comprehensive tests for error utility functions (18 tests)
• test/ui/user.test.ts - tests for user service functions (13 tests)
• test/ui/git-push.test.ts - expanded coverage for all git-push functions (13 tests)
• test/ui/repo.test.ts - expanded coverage for all repo functions (21 tests)

Tests cover success paths, HTTP errors (401/403/404/409/500), network failures, and edge cases.

Benefits

• Consistent error handling - all services use the same pattern
• Better UX - proper error messages shown to users
• Type safety - TypeScript ensures correct error handling
• Test coverage - prevents regressions and documents expected behavior

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	7290c33
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/6997082efcec110008bc81bc

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.37%. Comparing base (956d5e2) to head (7290c33).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1406      +/-   ##
==========================================
- Coverage   81.51%   81.37%   -0.15%     
==========================================
  Files          66       67       +1     
  Lines        4713     4735      +22     
  Branches      814      819       +5     
==========================================
+ Hits         3842     3853      +11     
- Misses        856      867      +11     
  Partials       15       15              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jescalada]

Looks good so far, thanks for all the extra UI tests!

What I had in mind when I first made the error handling refactor ticket was some sort of wrapper component (context?) that would catch any errors happening in API calls and forward the error to a toast. I'm aware this would require a lot of extra refactoring, so I might have to clarify the details and we can deal with it in a separate PR.

Note that I haven't tested behavior yet - will complete the review later this week 👍🏼

[kriswest]

Very happy to see this being done (particularly redirects to login on 401s and use of the API's error messages) and would love it to go into 2.0 (as the current situation is awful). I only have a couple of minor comments to add to Juan's.

[fabiovincenzi]

Looks good to me, and it covers #1402 , thanks @dcoric!