5.x cherry pick dev (#115)

* resolved conflicts

* resolved conflicts

* Update the documentation for procedures and functions to have up to date code examples from linked github repo. (#97) (#101)

Co-authored-by: Gem Lamont <106068376+gem-neo4j@users.noreply.github.com>

* Adding information about the version of junit used in the example (#103) (#106)

* adding information about the version of junit used in the example and note with instructions for users who want to keep using a previous version

* update after review

* removing incorrect extra lines

* adding the information that this can also be applied to neo4j 5 instead of just 4

* Update modules/ROOT/pages/extending-neo4j/procedures.adoc



---------

Co-authored-by: Jessica Wright <49636617+AlexicaWright@users.noreply.github.com>

---------

Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
Co-authored-by: Gem Lamont <106068376+gem-neo4j@users.noreply.github.com>
Co-authored-by: Lidia Zuin <102308961+lidiazuin@users.noreply.github.com>

Author: 4 people

modules/ROOT/pages/transaction-management.adoc

@@ -158,7 +158,7 @@ The existence of the `+SET n._LOCK_+` statement before the read of the `n.prop`
 [[transactions-locking]]
 == Default locking behavior
 
-* When adding, changing, or removing a property on a node or relationship a write lock is taken on the specific node or relationship.
+* When adding, changing, or removing a property on a node or relationship, a write lock is taken on the specific node or relationship.
 * When creating or deleting a node a write lock is taken for the specific node.
 * When creating or deleting a relationship a write lock is taken on the specific relationship and both its nodes.