Geant4InputHandling: prevent adding same particle more than once

Geant4InputHandling: collectPrimaries: use the mask to place the daughter vertices rather than size of the map

Now every place where interaction->vertices map is being used, the mask is used as the key to the map, instead of something else

If excited state is already known we get it via FindIon. Otherwise we use GetIon to create zero-state ions and print warnings for lvl>0

Geant4InputHandling: create G4PrimaryParticle with 4 vector that constrains also the mass, setting the mass after, affects the momentum

refactor the way rejectPDGs and leptonPDGs are passed through the reading of primary particles

 - in Geant4InputHandling.cpp

DDG4::InputHandling pass also particles with 0 lifetime to geant, only ignore quarks, gluons and 'strings'

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

use a vector instead of a map to make the order of particles deterministic and not depend on the memory layout
This is a problem if more than one primary particle exists.
Now runs with the same randomseed will produce the same result

Fixes crash when unknown particles (e.g. PDG 94) exist in the MCHistory
Should only be a problem if the MCGenerator does not write proper information

Support for multi-threaded Geant4 applications using DDG4Details are described in the release notes.