💡Improve User-Friendly Error Messages in modals

### Area

Proposal Pillar

### Is there new design needed?

Yes

### What?

Currently, error messages displayed to users in modals sometimes contain technical details or trace logs that are not meaningful to end users. This can lead to confusion and a poor user experience.

### Why?

- Improves user experience by providing clear, actionable messages.
- Reduces frustration by avoiding technical jargon.
- Helps users understand and resolve issues without requiring technical knowledge.
- Aligns with best practices for user communication.

### How?

- Review existing error messages across the application.
- Identify messages that contain stack traces, raw exceptions, or unclear technical terms.
- Replace these messages with clear, user-friendly descriptions.
- Ensure messages provide guidance on how to resolve the issue or where to get help.
- Maintain logging of technical details internally for debugging purposes without exposing them to users.

### (Optional) User Story with acceptance criteria

- [ ] All error messages presented to users are reviewed and updated where necessary.
- [ ] Error messages use clear, non-technical language.
- [ ] Messages provide actionable guidance where applicable.
- [ ] Internal logs still capture detailed technical errors for debugging.
- [ ] Changes are tested to ensure they appear correctly in the UI.