Improve disaster recovery page

[aarnq]

Describe the issue

The disaster recovery documentation needs an overhaul.

Ideally a disaster recovery documentation should provide a happy flow with only the restore from a scheduled backups, assuming everything is lost.

So I propose we rework the current page to a Back and Restore section that can also details how to do on-demand backups and restores (applicable for Grafana, OpenSearch and Velero) and a new Disaster Recovery documentation that pulls in the restore steps only.

With this we should also change the order to provide a better flow, minimise dev downtime, and take dependencies in consideration. Such as hint on restore of external dependencies to applications restored with Velero.

Additional context
Disaster recovery documentation should be able to be used and followed even in a high stress scenario, given that is what a disaster usually brings.

[cristiklein]

May I suggest we do this a 2-person task with one person from the MSE team and one person from the PS team?

[aarnq]

May I suggest we do this a 2-person task with one person from the MSE team and one person from the PS team?

I think that sounds like a great idea 👍