CMS7-8134: prepare for next development iteration

GOGREEN-1268: prepare release hippogogreen-3.09.02

"GOGREEN-34: prepare release hippogogreen-3.09.02-iteration-80

"GOGREEN-34: prepare release hippogogreen-3.09.02-iteration-79

"GOGREEN-34: prepare release hippogogreen-3.09.02-iteration-78

GOGREEN-1252 - Include the dist folder in the default profile to have the dist sub-module in the releaes cycle. Set the demo version to be the CMS release version

GOGREEN-1252: set demo.release.version to 7.9.0

CMS7-7821 new launchers based on swing application in executable jar

CMS7-7821 the launcher artifacts were updated, renamed and moved

"GOGREEN-34: prepare release hippogogreen-3.08.01-iteration-12

"GOGREEN-34: prepare release hippogogreen-3.08.01-iteration-11

"GOGREEN-34: prepare release hippogogreen-3.08.01-iteration-10

GOGREEN-1228: prepare branch hippogogreen-page-management

"GOGREEN-34: prepare release hippogogreen-3.08.01-iteration-9

"GOGREEN-34: prepare release hippogogreen-3.08.01-iteration-8

"GOGREEN-1209: prepare release hippogogreen-3.09.00-alpha-1

"GOGREEN-34: prepare release hippogogreen-3.08.01-iteration-7

"GOGREEN-34: prepare release hippogogreen-3.08.01-iteration-4

"GOGREEN-34: prepare for next development iteration

REPO-694: Drop JDO usage and support and replace by native JCR - warning: custom workflow extensions breakage
- some remaining TODOs are present in the code/configuration, marked with "TODO DEJDO"
  however all tests pass and work through the CMS or HST invoking common/custom workflow operations etc.

GOGREEN-1116: Use Demo Launcher version 0.5
  - Updated dist pom to use version 0.5

GOGREEN-1112: Generalization, handling and 'merging' of the platform launchers
  - Added demo-launchers profile
  - Updated the root README file to contain information on how to create the Demo Launchers
  - Demo Launchers file names now include the release version (e.g 7.8.1)

GOGREEN-1114: Created Demo Launchers do not create an appropriate directory structure and it might be annoying for users
  - In the dist-full profile I added another directory level under which the demo launchers are prepared before they are packaged and hence when (un)tarred/zipped the correct directory structure is created

GOGREEN-1112: Generalization, handling and 'merging' of the platform launchers
  - Added maven executions to:
  -# Download the maven deployed demo launchers and unpack them
  -# Bundle the built HGG with the launchers for different platforms
  -# Package each launcher with the bundled HGG
  -# Made these executions optional by un/setting the demo.launchers.skip system property

CMS7-6961: prepare for next development iteration

GOGREEN-1098: Dist configuration:
- Couldn't unify new behavior with old behavior or created a new profile (or re-created an old one)
- Profile: dist -- behaves the same as the old configuration; consistent with documentation and archetype
- Profile: dist-full -- new behavior for launcher which includes tomcat, expanded cms and site with initialized content

GOGREEN-1098: create a new dist configuration
- new dist module builds a 'raw' go-green distribution which includes tomcat, go-green cms and site and startup tutorial docs in the ROOT application (all expanded)
- repository content has been initialized already
- LICENSE and NOTICE files for the overall distribution
- build with $ mvn -P dist