Fullscreen error messages should be dismissable / Improve error handling for users

[zoglo]

Description

In my case, after unexpected actions such as a contao manager self update, the user should be able to either:

1. Close the error message
2. Reload the contao-manager

Right now the only action they have is clicking a link to a support page that leads them to 8 more options of finding help:
https://contao.org/de/support

Example

In my example, every Contao-Manager Self-Update will open the following success "Error" due to quickly changing the contao-manager.phar.php in the background, which does make sense to me but not for 99.9% of our users.

ERROR [200](https://developer.mozilla.org/de/docs/Web/HTTP/Status/200)
HTTP-Anfrage für "GET api/task" fehlgeschlagen.
Der Server hat eine Antwort mit Status-Code 200 gesendet.

I understand, from a developer perspective, why we would not want to have the user click away the error - so they can actually post about it.

What should the user do in this situation?
You can not interact anymore and the only action you have is a link to another page that offers you 8 more links:

How to solve / or improve this

• Provide a button to reload the Contao Manager?

• Provide a possibility to close this error, be it with a prompt that they could report the errror on this GitHub, such as in the other places?

• Improve on those edge-cases as they are not errors and make sure that a self update of the contao-manager doesn't suddenly throw an error

[aschempp]

This was meant to be like a blue screen on windows, where you would restart your computer. It should be obvioius that you can always reload in the browser. But technically, we could provide a button or at least a hint for it.