Add standard defined GQLSTATUS codes for data exceptions (#201)

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>

Author: 2 people

modules/ROOT/pages/errors/gql-errors.adoc

@@ -100,6 +100,14 @@ Status description:: error: connection exception - no such routing policy. Polic
 Database exceptions occur when a client request contains the wrong format, types, or other unsupported input.
 Some examples are data and constraint creation, which conflicts with existing constraints, properties of non-storable type, and spatial and temporal values with invalid components.
 
+=== 22000
+
+Status description:: error: data exception
+
+=== 22003
+
+Status description:: error: data exception - numeric value out of range. The numeric value `{ $value }` is outside the required range.
+
 === 22N00
 
 Status description:: error: data exception - unsupported value. The provided value is unsupported and cannot be processed.
@@ -435,9 +443,9 @@ Status description:: error: data exception - numeric range 0 disallowed. Expecte
 
 // Status description:: error: data exception - numeric range 0 or greater allowed. Expected a number that is zero or greater.
 
-// === 22N88
+=== 22N88
 
-// Status description:: error: data exception - not a valid CIDR IP. `{ $input }` is not a valid CIDR IP.
+Status description:: error: data exception - not a valid CIDR IP. `{ $input }` is not a valid CIDR IP.
 
 === 22N89