Epic: Replace toast notifications with some static component -> Activity Log

[lucasgoral]

Understand the problem

Our end users are presented important messages to see resources or confirm interaction

To allow confident usage of our tool, messages must stay visible, until user has seen them.

Toasts (auto-disappearing messages) are forbidden.

Context

Proposal Acceptance Criteria

• Toast notification is replaced by a component (e.g. Message Strip) that is static and user needs to actively close it
• Align to Creation of MCP: Show Success or Error in Modal, guide users where to find it next! [Remember: K8s is eventually consistent]

[andreaskienle]

Some candidates might be:

• Message Strip: Banner at the top somewhere
• Dialog to interrupt the user
• Inline error messages (like with other forms)
• Does it make sense to consider a notification center or something similar, even though we don’t have any user persistency?
• …

[n3rdc4ptn]

I guess it would still make sense to allow autodismissing toast or message popups, but we could improve the user experience by showing the dismissing delay in a loading bar at the bottom of the toast.

I guess a notification center could make sense, but we should exactly define which messages go there, informational stuff could get a lot if we put everything there.
Or we define it more like a notification history which just shows like an audit log so everyone can see what messages were posted

[n3rdc4ptn]

I guess we could talk about this in a Dev-Sync

[In-Ko]

As discussed, we first need to get the concept right, see #214.
So this very task here is going to be adjusted after we have the concept ready, and will likely become a bigger Epic with sub-tasks.