Create a better unified drawing methods

There are some features that could be shared between the DrawEvent methods.

For example, option arguments retrieval could be common. We could implement a common Drawing for event types using TRestHits.

Perhaps, it could be implemented at TRestEvent::DrawHitsEvent level the retrieval of options. Then, at TRestDetectorHitsEvent and TRestGeant4Event we could do:

TRestDetectorHitsEvent::DrawEvent( opt )
{
         TRestEvent::DrawHitsEvent( opt );

         // Write now specific drawing 
}

Another option is to create a new class TRestEventDrawer, that contains dedicated methods and the common drawing routines. Then TRestEvent could inherit from TRestEvent::TRestEventDrawer

This was discussed at rest-for-physics/detectorlib#33

Start by reviewing the DrawEvent methods in TRestEvent, TRestDetectorHitsEvent, and TRestGeant4Event, then read the related discussion in rest-for-physics/detectorlib#33. Compare the proposed TRestEvent::DrawHitsEvent and TRestEventDrawer designs. Done means shared option retrieval and drawing routines are consolidated without losing event-specific drawing behavior.