R25.03 Consistent error propagation in the portal from backend to frontend

[MaximilianHauer]

To be refined

Description

Currently we have multiple places where we inform the customer that an error happend but don't provide any information of the cause of the error as we don't use the specific error message raised in the backend.
I would like to enhance the frontend that we create a standardized behavior to display error messages in the frontend including the backend information.

Impact

Portal-Frontend
Portal-Backend

Benefit

Abstraction: The backend can handle complex errors without exposing implementation details to the frontend, simplifying the communication between the two layers.
Flexibility: The frontend can handle errors in a consistent way, regardless of the specific error that occurred on the backend.
Maintainability: Changes in the backend error handling logic do not necessarily require changes in the frontend, as long as the generic error representation remains consistent.

Committer

• @oyo
• @evegufy
• @ntruchsess

Additional information

• I'm willing to contribute to this feature