Store and extract more information from output geometry files

[eduard322]

Currently, there are a lot of geometry parameters that stored in yaml, json etc. configuration files (not mentioning even the geo parameters set as flags in macro/run_simScript.py). This makes almost impossible to decode what was going in the simulation from 202X year and to reproduce it. What can be done:

1. Store all the variables that are used to create geometry in the output file along with the geometry.
2. Propose condition that will allow either use them or not afterwards at the level of reco/analysis (where geo file is read to create a geometry again).

Current approach implies recreation of the geometry from root file using the parameters in the FairShip, so user uses relevant FairShip parameters instead of those used in the simulation.