fix: improve error handling

[ferruhcihan]

Implement

https://jira.linode.com/browse/APL-651

Description

This PR updates error handling for JWT errors.
Is paired with: linode/apl-api#681

Screenshots

Please check the ticket attachments.

Considerations

• I have tested the changes in both light and dark mode.
• I have considered the need for new unit tests.
• I have tested the changes on a cluster.
• I have included relevant documentation updates.
• I have an approved Figma design or have reflected my changes in Figma
• I have verified that the UI/UX is consistent in major browsers (e.g., Chrome, Firefox, Safari, Edge).
• I have tested the changes for responsiveness in different screen resolutions.
• I have tested expected error states and verified that the user is presented with informative error messages.
• I have tested the feature with unusual or extreme inputs (e.g., very long strings, empty states, clicking a button multiple times quickly).

[dennisvankekem]

When I get an error page and I navigate to another page I still get the error page because the Error state doesn't get reset. Can you fix that? Because now you need to either click the back button or refresh, otherwise the error does not go away

[CasLubbers]

Error page works for me ✅

[ferruhcihan]

When I get an error page and I navigate to another page I still get the error page because the Error state doesn't get reset. Can you fix that? Because now you need to either click the back button or refresh, otherwise the error does not go away

We’re able to reset some of the error states within the paper layout or the error component itself. However, if the error comes from external sources (api, global state or RTK queries) it’s more difficult to reset those automatically since they're managed outside of the layout.

That’s why we’ve added a back button, so users can safely navigate away and reinitiate the process when needed.