Geant4InputAction and Geant4EventReader: register input action into event reader enabling the event reader to access the Geant4 context

Improve the CMS example. Add word for the raw generator status of generator particles to Geant4Particle

- change Geant4PrimaryInteraction::VertexMap to
  std::map<int,std::vector<Vertex*>>

Use in event readers like:
MyReader::setParameters( std::map< std::string, std::string > & parameters ) {
  // int (or double, ...) m_parameter, defaultValue
    _getParameterValue( parameters, "MyParameters", m_parameter, defaultValue);
 }

 - changed signature of Geant4EventReader::readParticles(int,Vertex*, Particles&)
   to Geant4EventReader::readParticles(int,Vertices&, Particles& )
 - implement in LCIOEventReader, Geant4EventReaderHepEvt and Geant4EventReaderHepMC
 - for now still one vertex only is created using the first final state particle
   for HepEvt and LCIO

The event number was changed by each input source resulting in wrong behaviour.
Now the input sources keep track of the event number themselves.  Ideally the
event number would be kept track of one level above, but then m_firstEvent is
not known. Likewise the output module is not aware of the number of skipped
events.

Clearer status message in moveToEvent functions, change verbosity for particle printout in HepMC, add comment

Fix hundreds of std=c++11 compiler warningsAllow to change compiler settings in cmake/DD4hep.cmake valid for all packages.Watch out for CMAKE_CXX_FLAGS in cmake/DD4hep.cmake.Move to use Boost spirit::phoenix version 3. ---- Prepare for ROOT 6

No code changes. Common code formatting removing tabs, replacing with spaces (tab-size=-2) + emacs reformatting.

First implementation of dipole field, HepMC reader for DDG4 and fix to import constants into DDG4 python