Propagate LHCbApp.CondDBtag based on .Simulation
This avoids always adding two entries in CondDB.Tags, one for LHCBCOND and one for SIMCOND.
I discovered this bug since at
the moment there is no SIMCOND tag for DataType 2018 and
I set CondDBtag = "<latest:2018>", which in turn tries to
resolve the latest SIMCOND tag with this DataType.
This should be cherry picked in master. I'm not sure it needs to be propagated back to 2017, etc.
Edited by Rosen Matev