Fix Interface names, controller error handling, and RESTful API endpoints

[Copilot]

Swap Repository/Service interface and class names to correct layering pattern, add proper error handling to controllers, and adjust all endpoints to follow RESTful API best practices.

Changes Made

• Swapped Repository/Service interface and class names to correct layering pattern
• Updated all consumers: Controllers, DI registrations, cross-references
• Updated test files: renamed test classes, moved between folders, fixed namespaces
• Added try-catch blocks to all controller action methods with proper HTTP status codes (401, 409, 400, 404, 500)
• Auth-specific exceptions only caught in AuthController; non-auth controllers catch only domain-relevant exceptions
• Added new domain-specific exceptions: InterviewSessionNotFoundException, InterviewNotFoundException, DataValidationException
• InterviewSessionRepository throws InterviewSessionNotFoundException for null results
• UserRepository.ValidateUpdateUserDataAsync uses DataValidationException instead of auth exceptions
• Removed all controller test files (AuthControllerTest, InterviewControllerTest, InterviewSessionControllerTest, UserControllerTest, ProfilePictureControllerTest)
• Adjusted all endpoints to follow RESTful API best practices:
  • Routes use plural nouns and lowercase kebab-case (api/users, api/interviews, api/interview-sessions, api/profile-pictures)
  • Removed verbs from URLs — HTTP methods convey the action (e.g., GET api/users/me instead of GET api/User/get-current-user)
  • Resource hierarchy for sub-resources (api/interviews/hr, api/interviews/technical, api/interview-sessions/statistics)
  • Changed profile picture update from POST to PUT (replacing a resource)
  • Updated frontend endpoint definitions to match new backend routes
• All 109 remaining service/repository tests pass

[P1l3T0]

@copilot the code inside the controllers must be in a try catch block

[Copilot]

@copilot the code inside the controllers must be in a try catch block

Done in 8357e5b. All controller action methods are now wrapped in try-catch blocks that re-throw exceptions to be handled by the GlobalExceptionHandler.

[P1l3T0]

@copilot throw the actual errors, not just add the throw keyword

[Copilot]

@copilot throw the actual errors, not just add the throw keyword

Updated in 03aec1e. All catch blocks now capture the exception in a variable and throw it explicitly: catch (Exception ex) { throw ex; }.

[P1l3T0]

@copilot for the controllers, they should return the corresponding HTTP status code based on the success or failure of the operation, adjust them accordingly, especially the Authentication related ones

[Copilot]

@copilot for the controllers, they should return the corresponding HTTP status code based on the success or failure of the operation, adjust them accordingly, especially the Authentication related one...

Done in a5eebdf. All controllers now catch specific exceptions and return the corresponding HTTP status codes:

• InvalidCredentialsException, NoUserLoggedInException, InvalidAccessTokenException, InvalidRefreshTokenException → 401 Unauthorized
• UserAlreadyExistsException → 409 Conflict
• EmptyFieldsException, UnsupportedFileExtensionException, ProfilePictureException → 400 Bad Request
• ResourceNotFoundException → 404 Not Found
• Generic Exception → 500 Internal Server Error

[P1l3T0]

@copilot You didn't understand, I meant I want auth-related exceptions for the auth controller only, for the others i do not want the following in them, because they are not related to authentication at all:

catch (InvalidCredentialsException ex)
{
    return Unauthorized(ex.Message);
}
catch (UserAlreadyExistsException ex)
{
    return Conflict(ex.Message);
}
catch (EmptyFieldsException ex)
{
    return BadRequest(ex.Message);
}

Now review what the services do and the current custom exceptions and try to add new custom exceptions to the services/repositories if you find any use for them

[Copilot]

@copilot You didn't understand, I meant I want auth-related exceptions for the auth controller only, for the others i do not want the following in them, because they are not related to authentication ...

Done in b76f146 and ce9a73a.

Changes made:

• Removed InvalidCredentialsException, UserAlreadyExistsException, and EmptyFieldsException catches from all non-auth controllers (InterviewController, InterviewSessionController, UserController, ProfilePictureController)
• Added new domain-specific exceptions: InterviewSessionNotFoundException, InterviewNotFoundException, DataValidationException
• InterviewSessionRepository now throws InterviewSessionNotFoundException when sessions are not found (GetAdjacentInterviewSessionAsync, GetInterviewSessionByIdAsync, GetInterviewSessionFromQuestionsAsync)
• UserRepository.ValidateUpdateUserDataAsync now throws DataValidationException instead of auth-related exceptions
• Each controller only catches exceptions relevant to its domain:
  • AuthController: InvalidCredentialsException, UserAlreadyExistsException, EmptyFieldsException, InvalidRefreshTokenException, NoUserLoggedInException
  • InterviewController: InterviewSessionNotFoundException, ResourceNotFoundException
  • InterviewSessionController: InterviewSessionNotFoundException
  • UserController: DataValidationException, ResourceNotFoundException
  • ProfilePictureController: UnsupportedFileExtensionException, ProfilePictureException

[P1l3T0]

@copilot okay cool, now I want you to remove all tests related to the only the controllers, leave the rest

[Copilot]

@copilot okay cool, now I want you to remove all tests related to the only the controllers, leave the rest

Done in f73081d. Removed all 5 controller test files (AuthControllerTest, InterviewControllerTest, InterviewSessionControllerTest, UserControllerTest, ProfilePictureControllerTest). The remaining 109 service/repository tests all pass.

[P1l3T0]

@copilot adjsut the endpoints to follow the best practices for RESTful APIs

[Copilot]

@copilot adjsut the endpoints to follow the best practices for RESTful APIs

Done in c1622fd. All endpoints now follow RESTful best practices:

• Routes: plural nouns, lowercase kebab-case (api/users, api/interviews, api/interview-sessions, api/profile-pictures)
• No verbs in URLs: HTTP methods convey the action (e.g., GET api/users/me instead of GET api/User/get-current-user)
• Resource hierarchy: api/interviews/hr, api/interviews/technical, api/interview-sessions/statistics, etc.
• Proper HTTP methods: profile picture update changed from POST to PUT
• Frontend endpoints updated to match