Update config files for CC analysis toolchain

[jminock]

Describe your changes

Updates to CC analysis ToolChain config files to reflect needs of analysis and updated Tools.

EventSelector: Added TriggerWord to satisfy changes in PR #311 and turning off cuts to include potential background events.

FindMrdTracks: Output file is not necessary for CC analysis. Turning off to reduce clutter.

LoadGenieEvent: Verbosity turned down to reduce terminal clutter; can be turned up if needed. Everything else is to load in GENIE file in pwd and automatically match events to corresponding wcsim events. This allows correct GENIE to WCSim event alignment for tank and world samples. Previous configuration only worked for tank samples.

LoadReweightGenieEvent: Same as above. Also includes new weight configuration to match uB. Additional "All" weights are necessary with respective random seeds. Furthermore, the number of universes for "All" was decreased from 1000 to 100. So in addition to matching uB for joint analysis, run time is faster and the resultant ntuple file will take up less space.

LoadWCSim: Loads in WCSim file in pwd. Defaults to run 0, subrun 0. A bug exists where LoadWCSim cannot load in WCSim files from /pnfs/ directly.

LoadWCSimLAPPD: Same as above.

MCRecoEventLoader: Verbosity turned down to reduce terminal clutter; can be turned up if needed. Turning of particle selection to include potential background events.

ToolChain can run with all changes implemented.

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
• [ NA ] If this PR includes a new Tool, a README and minimal demonstration ToolChain is provided
• [ NA ] 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
• [ NA ] For every new usage, there is a reason the data must be on the heap
• [ NA ] For every new there is a delete, unless I explicitly know why (e.g. ROOT or a BoostStore takes ownership)

Additional Material

NA