Add example for new notification "Binding a variable-length relations… (#64)

Cherry-picked from #40 

- Removing deprecation examples for "repeated variable length
relationship references" since they are being "undeprecated".
- Adding example `Binding a variable-length relationship variable more
than once` to demonstrate a new notification.

Build on top of #35.

Co-authored-by: Gustav Hedengran <[email protected]>

Author: renetapopova

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

@@ -686,68 +686,6 @@ m|WARNING
 m|DEPRECATION
 |===
 
-.Repeated variable length relationship variable inside the same pattern, with same relationship type (when run on a 5.x release)
-====
-Query::
-+
-[source,cypher]
-----
-MATCH ()-[r:PARENT*]-()
-MATCH ()-[r:PARENT*]-()
-RETURN *
-----
-
-Description of the returned code::
-Using an already bound variable for a variable length relationship is deprecated and will be removed in a future version. (the repeated variable is: `r`)
-
-Suggestions for improvement::
-Inside a single pattern, we have relationship uniqueness, which means that this query never will return any rows and should therefore be rewritten to the wanted behavior.
-
-====
-
-.Repeated variable length relationship across patterns, with the same relationship type
-====
-Query::
-+
-[source,cypher]
-----
-MATCH ({name:"Molly"})-[r:KNOWS*]->({name:"Kalle"})
-MATCH ({age:25})-[r:KNOWS*]->({age:21})
-RETURN r
-----
-
-Description of the returned code::
-Using an already bound variable for a variable length relationship is deprecated and will be removed in a future version. (the repeated variable is: `r`)
-
-Suggestions for improvement::
-Since the relationships in the first and second match must be the same, we know that the start node and the end node are the same.
-In the query above, we could therefore concatenate the predicates from the two matches and create a single match:
-+
-[source,cypher]
-----
-MATCH ({name:"Molly", age:25})-[r:KNOWS*]->({name:"Kalle", age:21})
-RETURN r
-----
-====
-
-.Repeated variable length relationship across patterns with different relationship types
-====
-Query::
-+
-[source,cypher]
-----
-MATCH ()-[r:PARENT*]-()
-MATCH ()-[r:CHILD*]-()
-RETURN *
-----
-
-Description of the returned code::
-Using an already bound variable for a variable length relationship is deprecated and will be removed in a future version. (the repeated variable is: `r`)
-
-Suggestions for improvement::
-Since the relationships in the first and second match must be the same, and a single relationship can't have multiple relationship types, this query will never return any rows.
-====
-
 .Colon after the | in a relationship pattern
 ====
 Query::
@@ -1144,9 +1082,7 @@ Relationship type expression cannot possibly be satisfied. (`R1&R2` can never be
 ====
 
 [#_neo_clientnotification_statement_repeatedrelationshipreference]
-=== RepeatedRelationshipReference
-
-label:introduced-in-Neo4j-5.5[Introduced in Neo4j 5.5]
+=== Neo.ClientNotification.Statement.RepeatedRelationshipReference
 
 .Notification category details
 [cols="<1s,<4"]
@@ -1161,7 +1097,7 @@ m|WARNING
 m|GENERIC
 |===
 
-.Binding a relationship variable more than once
+.Binding a relationship variable more than once (when run on version 5.5 or newer)
 ====
 Query::
 +
@@ -1180,3 +1116,15 @@ Use one pattern to match all relationships that start with a node with the label
 MATCH (:A)-[r]->(:B) RETURN r
 ----
 ====
+
+.Binding a variable-length relationship variable more than once (when run on version 5.6 or newer)
+====
+Query::
++
+[source,cypher]
+----
+MATCH ()-[r*]->()<-[r*]-() RETURN count(*) AS count
+----
+Description of the returned code::
+A variable-length relationship variable is bound more than once, which leads to no results because relationships must not occur more than once in each result. (Relationship r was repeated)
+====