Change parameter serverName to server (#287)

As this change will not be visible to the user when they get the error,
I opted for not including it in changelog/mark as changed in 2025.04.
Let me know if you think otherwise.

Co-authored-by: Reneta Popova <[email protected]>

Author: Lojjs

modules/ROOT/pages/notifications/all-notifications.adoc

@@ -4012,7 +4012,7 @@ m|TOPOLOGY
 m|03N85
 |Status description
 a|
-info: server has caught up. Server `{ $serverName }` at address `{ <<serverAddress>> }` has caught up.
+info: server has caught up. Server `{ <<server>> }` at address `{ <<serverAddress>> }` has caught up.
 |Classification
 m|TOPOLOGY
 |SeverityLevel
@@ -4082,7 +4082,7 @@ m|TOPOLOGY
 m|01N80
 |Status description
 a|
-warn: server failed. Server `{ $serverName }` at address `{ <<serverAddress>> }` failed: `{ <<msg>> }`
+warn: server failed. Server `{ <<server>> }` at address `{ <<serverAddress>> }` failed: `{ <<msg>> }`
 |Classification
 m|TOPOLOGY
 |SeverityLevel
@@ -4158,7 +4158,7 @@ m|TOPOLOGY
 |GQLSTATUS code
 m|01N81
 |Status description
-a|warn: server is catching up. Server `{ $serverName }` at address `{ <<serverAddress>> }` is still catching up.
+a|warn: server is catching up. Server `{ <<server>> }` at address `{ <<serverAddress>> }` is still catching up.
 |Classification
 m|TOPOLOGY
 |SeverityLevel
@@ -4236,7 +4236,7 @@ m|TOPOLOGY
 |GQLSTATUS code
 m|01N82
 |Status description
-a|warn: server is not available. Server `{ $serverName }` is not available.
+a|warn: server is not available. Server `{ <<server>> }` is not available.
 |Classification
 m|TOPOLOGY
 |SeverityLevel