add info about deprecated notification api and swap the code examples

Author: renetapopova

modules/ROOT/pages/draft.adoc

@@ -20,4 +20,13 @@ The ultimate goal is to have a 1-1 mapping between a GQLSTATUS code and a specif
 
 If a Neo4j error matches a standard-defined condition and subcondition, then the standard-defined GQLSTATUS code should be used for that error. For instance, (Neo.ClientError.Statement.ArithmeticError, ArithmeticException, “/by zero”) matches the “data exception” condition and “division by zero” subcondition in GQL (i.e., 22012 GQLSTATUS code).
 
-error: data exception - string data, right truncation
+error: data exception - string data, right truncation
+
+
+
+Processing of GQL-requests can cause various conditions to be raised. Each such condition is identified by a unique code called GQLSTATUS, which is a character string that always includes a class code that specifies the principle category to which the condition belongs. It may also include a subclass code that specifies additional information about the reason for raising the condition. The exact format of GQLSTATUS codes is specified in Subclause 23.1, “GQLSTATUS”.
+For example, the GQLSTATUS '22003' identifies the exception condition “data exception — numeric value out of range”.
+The GQLSTATUS codes assigned by this document to conditions are stable and can be depended on to remain constant.
+There are two types of conditions:
+— completion conditions.
+— exception conditions.

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

@@ -3,7 +3,7 @@
 [[listOfNnotifications]]
 = List of all server notification codes
 
-The following page provides an overview of all notifications in Neo4j, including the GQLSTATUS codes and the legacy Neo4j codes, along with some scenarios and their possible solutions.
+The following page provides an overview of all notifications in Neo4j, including the GQLSTATUS codes and Neo4j legacy codes, along with some scenarios and their possible solutions.
 
 * <<_performance_notifications, `PERFORMANCE` notifications>>
 * <<_hint_notifications, `HINT` notifications>>
@@ -3369,7 +3369,7 @@ Use `DATABASE *` without the parameter to revoke the privilege on all databases.
 .Notification details
 [cols="<1s,<4"]
 |===
-|Neo4j code
+|Neo4j legacy code
 m|Neo.ClientNotification.Security.AuthProviderNotDefined
 |Title
 a|The auth provider is not defined.
@@ -3485,7 +3485,7 @@ If it is correct, make sure to add it as a known auth provider in one or both of
 .Notification details
 [cols="<1s,<4"]
 |===
-|Neo4j code
+|Neo4j legacy code
 m|Neo.ClientNotification.Security.ExternalAuthNotEnabled
 |Title
 a|External auth for user is not enabled.

modules/ROOT/pages/notifications/index.adoc

@@ -7,6 +7,7 @@ After a successful query execution, the Neo4j server sends notifications to prov
 The driver receives these notifications and sends them to the client, which displays them to the user.
 
 From version 5.23, Neo4j has a new GqlStatusObject API in addition to the existing Notification API.
+The Notification API is deprecated since Neo4j 5.26.
 The GqlStatusObject API provides information about the status of a Cypher query or command execution in compliance with the GQL standard.
 
 This page describes both the GQL-status object and the Neo4j Notification frameworks, how they are structured, the objects they provide for notifications, and how to interpret them.
@@ -148,18 +149,19 @@ The following table lists the Neo4j-defined groups of GQLSTATUS codes and their
 
 |===
 
-[[neo4j-notification-object]]
-== Neo4j notification object
+[role=label--deprecated-5.26]
+[[legacy-notification-object]]
+== Legacy notification object
 
-The Neo4j notification object contains diagnostic information representing the successful outcome of a Cypher query or command execution, including severity, the `ClientNotification` code, category, title, description, and position in the query text where the notification is relevant.
+The Neo4j legacy notification object contains diagnostic information representing the successful outcome of a Cypher query or command execution, including severity, the `ClientNotification` code, category, title, description, and position in the query text where the notification is relevant.
 Depending on the application, some of the fields from the notification object might not be visible.
 
-The notification object consists of the following fields:
+The legacy notification object consists of the following fields:
 
-.Neo4j notification object
+.Neo4j legacy notification object
 [cols="<1s,<4"]
 |===
-|Neo4j code
+|Neo4j legacy code
 a|The Neo4j status code in the form of `Neo.ClientNotification.[SubType].[Name]`.
 |Title
 a|The title of the Neo4j status code.
@@ -244,6 +246,7 @@ The following notification groups exist in Neo4j, ordered by severity:
 |
 |===
 
+[role=label--deprecated-5.26]
 [[notification-internals]]
 == Notification internals
 
@@ -252,7 +255,7 @@ During the handshake process, they agree on using the newest possible Bolt proto
 For more information on the Bolt versions supported by different server versions, see the link:https://neo4j.com/docs/bolt/current/bolt-compatibility[Bolt Protocol documentation].
 
 On the server side, notifications are part of the Result Core API.
-A method called `getNotifications()` returns a list of server-side notification objects.
+A method called `getNotifications()`, which is deprecated since 5.26, returns a list of server-side notification objects.
 These notifications are then sent to the driver as success Bolt message metadata.
 On the driver side, notifications are part of the ResultSummary API, which has a method called `notifications()` that returns a list of driver-side Notification objects.
 The result of the `getCode()` or `code()` methods is known as the Neo4j status code.
@@ -261,6 +264,7 @@ For more information, see <<notification-grouping-and-filtering, Server notifica
 
 From version 5.23, Neo4j has a new GqlStatusObject API in addition to the existing Notification API.
 This can be used using the `.getGqlStatusObjects()` method in the Result Core API or by using the latest Neo4j drivers.
+The Notification API is deprecated since Neo4j 5.26.
 
 [[server-driver-compatibility]]
 == Server-driver version compatibility