CMS7-6404 no need for explicit node or property spec for insert, whether the statement refers to a node or a property can already be read from the patch string like is done when parsing the update statement

CMS7-6404 human readable jcr diff format. serialization part is all done, deserialization part is still pending insert node operation. something must still be done about reading multi-line string values. also error messages and logging must still be improved

CMS7-6404: As a Developer, I want to be able to read and edit my patches for the new updater console features in an easy format
- Applying the 1st comment from Frank
- Also removed some warnings indicated by IntelliJ

CMS7-6404: As a Developer, I want to be able to read and edit my patches for the new updater console features in an easy format
- Fixed the updates problem
- Added tests for that
- 1 down one to go (the paths problem)

CMS7-6380: changed scope of easymock dependencies to 'test'
Also moved all dependencies to the dependencyManagement section of the root pom, and defined all versions as properties. Reused properties from the project pom where possible.

CMS7-6095: root javascript element xss get transformed into head script xss
XSS which is part of a head element with no following body element is not getting removed. The neko parser transforms the html structure, if no body element is present the HtmlRepairer is throwing an exception. The html-element cleanup method is split up into html- and head-element, in case the body-element is reached the head-element method is skipping further processing.

HTMLCLEANER-39 the cleanupStartElement method is complex and it's descended method calls have duplicate code
The method and sub methods of cleanupStartElement are refactored and simplified. The elements are passing cleanUpAttributes and are set depending if after the cleanup elements without attributes are deleted or not.