Description:
Currently, business-specific exceptions are thrown in various places across the codebase without a unified structure. To improve maintainability and provide users with clear and meaningful error messages, we should introduce custom exception classes tailored to different business error scenarios.

Some occurrences of these exceptions can be identified by searching for "TODO Candidate for custom exception", while others may require a manual review of the codebase. The goal is to replace generic exceptions with well-defined custom ones, ensuring that error messages are consistent, user-friendly, and easy to handle both in the UI and logs.

Additionally, if a global exception handling mechanism is in place, it should be updated to properly format and manage the new custom exceptions. If no such mechanism exists, consider implementing one to centralize error handling and improve debugging.

The primary focus is on structuring error handling in a way that enhances maintainability, readability, and user experience, without altering the intended functionality of the system.