Improve physics process store

[lobis]

Related PR: rest-for-physics/restG4#55

Currently Geant4 process names - id relation are being stored in a hardcoded map on TRestGeant4Track.

This PR provides a container class, TRestGeant4PhysicsInfo that stores this information (which can be different across Geant4 versions) without adding noticable overhead.

Additionally this class can be used to print which particles or processes took place in the simulation for a quick overview:

const auto& physicsInfo = (TRestGeant4Metadata*)run.GetMetadataClass("TRestGeant4Metadata")->GetGeant4PhysicsInfo();
physicsInfo.Print(); // Notice how this isn't a pointer! its an immutable reference

Particles:
	11 - e-
	22 - gamma
Processes:
	1091 - Transportation
	2002 - eIoni
	2003 - eBrem
	2010 - msc
	2011 - Rayl
	2012 - phot
	2013 - compt
	7401 - e-Step

Since Geant4 does not provide a way to generate a processID (only provides process name) I created one which should be unique (process->GetProcessType() * 1000 + process->GetProcessSubType()). This breaks compatilibty with old versions of REST where processes where using the manual assignment found on TRestGeant4Track.

This PR also deprecates some methods related to processes, which in my opinion were too specific, redundant, or were not garanteed to work in the current version. Methods such as isPhotoElectric have been replaced by the more generic ContainsProcess

Now also print methods for event or track have access to the corresponding metadata class to access the volume / process names, so now print statements are more user readable, showing volume names instead of IDs and showing the Geant4 process names instead of the hardcoded ones.

[lobis]

@juanangp could you also please review the related PR? rest-for-physics/restG4#55 ty