fix(heureka): gracefully handle fatal errors

[taymoor89]

Summary

Previously when there was a fatal error in case of broken API Heureka wasn't even displaying app layout. Now using ErrorBoundary the fatal errors that typically happen because of a rejected promise are gracefully handled and displayed inline.

Changes Made

• Moved App header outside of the router.
• If an error boundary is missing the root route catches the error and displays it.
• Errors are displayed inline where they happen instead of always displaying them on top which makes user experience better.
• Removed MessagesProvider as it is not need at the moment.

Related Issues

• [Task](heureka): Error Handling and App Crashes #847

Screenshots (if applicable)

2025-10-08_11-55-10.mp4

2025-10-08_11-56-05.mp4

2025-10-08_11-57-23.mp4

Testing Instructions

1. pnpm i
2. pnpm TASK

Checklist

• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have made corresponding changes to the documentation (if applicable).
• My changes generate no new warnings or errors.
• I have created a changeset for my changes.

PR Manifesto

Review the PR Manifesto for best practises.

[changeset-bot]

🦋 Changeset detected

Latest commit: ec8a203

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@cloudoperators/juno-app-heureka	Patch
@cloudoperators/juno-app-greenhouse	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

PR Preview Action v1.6.2
Preview removed because the pull request was closed.
2025-10-30 14:00 UTC

[ArtieReus]

Very good job I like how you have designed it. I just added 2 comments and one of them is about testing. Would it make sense at that stage at least for the new files introduced to add some tests?

[hodanoori]

Great work, thanks Taimoor. Please address the following case in this PR as well, as we discussed it this morning in our team round:

Display a loading indicator inside the filter selects while waiting for the GetServiceFilters request to complete, and if that request fails, show an appropriate “Failed to load filters” message inside Filter selects.
However, the services list should still render and remain usable (including search functionality and navigate to other panel or pages view).

[ArtieReus]

Shouldn't here display another kind of error here?

[ArtieReus]

I was able to get a black screen with following initialFilters:

  "initialFilters": {
    "support_group": ["containerss"]
  },

[taymoor89]

I was able to get a black screen with following initialFilters:

  "initialFilters": {
    "support_group": ["containerss"]
  },

That was from Hoda's PR, this should not happen in this PR.

[taymoor89]

Shouldn't here display another kind of error here?

True I fixed it, but in this PR the kind or the text of the error message is not important the most important thing is that the app should not crash in any case backend or user input failure.

[ArtieReus]

Great job!! Thx!!