Improve error handling for OCL Mapper (avoid blank screen and page crash)

[filiperochalopes]

User story

As a user, I want Match API errors to be displayed accurately (per row) and maybe one general popover message to know there was an error in the process so I can understand failures without the page breaking.

Use case

Run OCL Mapper with a custom Match API and review row-level results and errors.

Requirements

• Do not crash the page or show a blank screen when external Match API calls fail.
• Ensure a general popover is shown when any errors come from match APIs (with a link to open the first related row with the error)
• Ensure errors are surfaced per row (not only logged/recorded).
• Handle and display common error cases:
  • 401 Unauthorized (e.g., typo in token configuration)
  • 504 Gateway Timeout (prolonged processing)
  • 500 Internal Server Error (other Match API issues)
• Use a standard UI pattern/component for error display (e.g., popover) if available.

Acceptance criteria

• Given a row triggers a 401/500/504 from the external Match API, then the page remains usable and does not render blank.
• The affected row shows an error state/message that indicates the HTTP status (401/500/504) and that the failure came from the external Match API.
• Errors continue to be recorded/logged per row.