Conflict because RooUnfold ships TUnfold

The following discussion from !148 (merged) should be addressed:

• @lmoureau started a discussion: (+3 comments)

  Gotta figure out what to do with this (in LCG). It seems RooUnfold just decided that it would also provide TUnfold. Maybe we could namespace our version or override some naming macro...

  Warning in <TInterpreter::ReadRootmapFile>: class  TUnfoldBinningV17 found in libRooUnfold.so  is already in libTUnfold.so 
  Warning in <TInterpreter::ReadRootmapFile>: class  TUnfoldBinningXMLV17 found in libRooUnfold.so  is already in libTUnfold.so 
  Warning in <TInterpreter::ReadRootmapFile>: class  TUnfoldDensityV17 found in libRooUnfold.so  is already in libTUnfold.so 
  Warning in <TInterpreter::ReadRootmapFile>: class  TUnfoldIterativeEMV17 found in libRooUnfold.so  is already in libTUnfold.so 
  Warning in <TInterpreter::ReadRootmapFile>: class  TUnfoldSysV17 found in libRooUnfold.so  is already in libTUnfold.so 
  Warning in <TInterpreter::ReadRootmapFile>: class  TUnfoldV17 found in libRooUnfold.so  is already in libTUnfold.so

  It may be worth opening an issue with RooUnfold.