Some Geo Mermaid diagrams are hard to read in version 11

We would like to upgrade to Mermaid 11, but some of our diagrams look worse in the new version. In particular, some of the most simple diagrams are getting text cut off. We should update them to work in Mermaid 11 before we upgrade to it.

• MR that fixed other diagrams: !197387 (merged)
• Issue describing the incompatibilities #554889

Here's a list of the affected diagrams:

v 11	Docs url	Source page
	https://docs.gitlab.com/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node/	link
	(https://docs.gitlab.com/administration/geo/disaster_recovery/runbooks/planned_failover_single_node/)	link
	https://docs.gitlab.com/administration/geo/glossary/	link
	https://docs.gitlab.com/administration/geo/glossary/	link
	https://docs.gitlab.com/administration/geo/glossary/	link

Proposal

Since those diagrams are just showing a static architecture with no connections between nodes, it's better to convert them to a table or a list structure instead of a Mermaid diagram. This would be more appropriate for a static topology diagram anyway. For example turn https://gitlab.com/gitlab-org/gitlab/-/blob/7c3af9f178c2f32aaafece4105a691c0df84f6e0/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md#geo-planned-failover-for-a-multi-node-configuration into:

## Geo planned failover for a multi-node configuration

| Component   | Configuration                |
|:------------|:-----------------------------:|
| PostgreSQL  | Managed by the Linux package |
| Geo site    | Multi-node                   |
| Secondaries | One                          |

This runbook guides you through a planned failover of a multi-node Geo site
with one secondary (a 40 RPS / 2,000 user reference architecture is assumed).

Primary Site (Multi-node):
- Rails node 1
- Rails node 2
- PostgreSQL node
- Gitaly node
- Redis node
- Monitoring node

Secondary Site:
- Rails node 1
- Rails node 2
- PostgreSQL node
- Gitaly node
- Redis node
- Monitoring node

...