UI - PPR - Error message handing

For both MHR and PPR

### User Story
As a user, when an API error occurs in PPR, I want to see a clear and actionable error message so that I can understand and resolve the issue efficiently.

---

### Context
Popups currently fail to provide meaningful feedback. Users are left guessing which fields are missing or incorrect. This leads to frustration and delays in resolving issues.

---

### Tasks

- [ ] Review existing error messages to assess clarity and usefulness.
- [ ] Identify which messages lack sufficient explanation.
- [ ] Improve error handling for popups that currently fail to indicate the cause of issues.

### Expected Behavior
When a data error occurs in a PPR transaction, the system should:
- Clearly identify the field(s) in error.
- Explain why the error occurred (e.g., missing required field, invalid format).
- Highlight the problematic field visually in the UI.

### Support Enhancements
Include the following in error modals where applicable:
- Account number
- Timestamp
- Copy-to-clipboard button for the full API error response, enabling users to easily share with the OPS team.

No source files or tests are named. Start by locating the PPR and MHR popup error-handling entry points, then review how API errors are currently displayed. Done means actionable field-level messages, visual highlighting, and the specified modal details where applicable.

Written by the indexing model from the issue text.