Fix scoping of maven enforcer evaluations

By default maven enforcer uses global scope of variables.
That means that during parallel builds (-T maven option) its possible
that variables with the same name used in different modules enforcer rules
will interfere.
PR changes scoping of variables to be local instead of global.

pom.xml

@@ -656,7 +656,7 @@
             <rules>
               <evaluateBeanshell>
                 <message>Maven module has to be in a "groupId" beginning with "org.neo4j"</message>
-                <condition>String s = "${project.groupId}"; s.startsWith("org.neo4j")</condition>
+                <condition>{String s = "${project.groupId}"; s.startsWith("org.neo4j");}</condition>
               </evaluateBeanshell>
               <requireFilesDontExist>
                 <message>You are not allowed to have classes in "com" package</message>