[Refactor] Reduce repetitive error handling patterns in use cases

[kamiazya]

Problem Description

Similar error handling patterns are repeated across methods in use case classes, violating the DRY (Don't Repeat Yourself) principle and making maintenance more difficult.

Example Location

contexts/scope-management/application/src/main/kotlin/io/github/kamiazya/scopes/scopemanagement/application/usecase/ValidateAspectValueUseCase.kt

The invoke(Query) and executeMultiple() methods contain nearly identical error handling logic that could be extracted.

Current Code Pattern

Repetitive patterns like:

• Similar validation logic across multiple methods
• Duplicate error transformation code
• Repeated fold operations with similar left/right handling

Proposed Solution

1. Extract common error handling into private helper functions
2. Utilize Arrow's Raise DSL more effectively for cleaner error handling
3. Create reusable validation utilities where appropriate

Task Breakdown

• Identify all use cases with repetitive error handling
• Design common error handling patterns/utilities
• Refactor ValidateAspectValueUseCase as pilot
• Apply pattern to other use cases
• Update tests to cover refactored code
• Document the new error handling patterns

Benefits

• Improved maintainability
• Easier to modify error handling logic
• Reduced code duplication
• More consistent error handling across use cases

Difficulty

Intermediate - Requires understanding of functional error handling patterns and Arrow library

References

• Arrow documentation on Raise DSL
• Project error handling guidelines