Changes to TreeMaker logic to handle new MC waveforms

[S81D]

Describe your changes

This PR is dependent on Andrew's new PMTWaveformSim tool (#324). His new tool generates waveforms from MC hits and runs the data hit finding tool (PhaseIIADCHitFinder) over the MC waveforms. Those hits are saved in the same pulse vector as the data hits. The logic of the PhaseIITreeMaker needed to be changed to handle data-like hits for MC events. Essentially just added some if / else statements to make sure this tool handles the MC waveform hits just like the data while keeping functionality for other MC truth information.

Other downstream tools will need to be adjusted; I will open separate PRs for each of those tools.

Checklist before submitting your PR

• This PR implements a single change (one new/modified Tool, or a set of changes to implement one new/modified feature)
• This PR alters the minimum number of files to affect this change
• [N/A] If this PR includes a new Tool, a README and minimal demonstration ToolChain is provided
• If a new Tool/ToolChain requires model or configuration files, their paths are not hard-coded, and means of generating those files is described in the readme, with examples provided on /pnfs/annie/persistent
• [N/A] For every new usage, there is a reason the data must be on the heap
• [N/A] For every new there is a delete, unless I explicitly know why (e.g. ROOT or a BoostStore takes ownership)

Additional Material

See Andrew's PR for details (#324). If you want to use the MC waveform hits, ensure the configuration for PhaseIITreeMaker has both IsData 0 (indicating it is MC) and PMTWaveformSim 1. Setting the latter to 0 will use the default MC hits created by summing the individual photon hits in the ClusterFinder tool