Create UI: there should be an error dialog if Keycloak token is expired/invalid

Check with Relationships team to work on this.

### Title: Keycloak Expired or Invalid

----

Currently there is no error dialog if the dashboard cannot be loaded because my JWT is expired or invalid. The purpose of this ticket is to implement a message (dialog) when the user's Keycloak token is expired or invalid.

This fix should also be implemented for the new Edit UI.

See also #2378 and #2493. These tickets are not duplicates but highly related.

~This ticket should be implemented AFTER the "new" Keycloak validation is implemented in create-business so that that functionality can be used here. (Otherwise, we can only check if the token has expired, not if it's valid.)~ _This is now implemented but I think we still can't tell if the KC isvalid._

## Description:
* As a user
* I want a specific notification when my business dashboard is unavailable because my Keycloak token is expired or invalid
* so that I know my problem is authentication not authorization.

**Acceptance Criteria**
* GIVEN ... (you or your condition)
* WHEN ... (what you do)
* THEN ... (what you see)

**Dependencies? (If so, link dependency in the ticket, make it visible in a team´s backlog)**

**Validation Rules? (If yes, list here)**

----

**DoR for User Story:**
- [ ] Do we have a prioritized Sprint Backlog?
- [ ] Defects, user stories and other work the team has committed to are contained in the sprint backlog?
- [ ] Any hidden work?
- [ ] All team members availability (days) & capacity (in SP) is known for the Sprint?
- [ ] All users stories meet the DoR?

**Definition of Ready:**
1. [ ] Does User Story have full flow of business rules, happy and alternate paths, etc.?
2. [ ] Requirements & expected behavior included in the User Story?
3. [ ] Are the dependencies known/ understood?
4. [ ] Dev team accepts user experience artifacts
5. [ ] If there are validation rules, are they defined (UI, Data, Role-Action)?
6. [ ] Does this User Story needs stakeholder approval?
7. [ ] Is this user story small enough to be completed in a Sprint?
8. [ ] What do we possible have to do re Change Management? - a) GCPE, …?

----

**Definition of Done:**
1) [ ] Check Requirements against completed tasks
2) [ ] Completed stories verified in Dev and Test
3) [ ] Confirm Test cases built and succeeding
4) [ ] No regression test failures
5) [ ] Test coverage acceptable by Product Owner???
6) [ ] Ticket merged to master or story branch
7) [ ] Developer to list Config changes/ Update documents and designs
8) [ ] Design / Solution accepted by Product Owner
9) [ ] UX Approved
10) [ ] Can be demoed in Sprint Review
11) [ ] Release ticket is created and this US is linked to it