Make running doAll_Zp more flexible and setup for condor jobs

[VourMa]

This PR adds command line arguments to doAll_Zp and includes a wrapper for running it. The wrapper can be used locally but can also be the basis for running on batch.

• cpp/runOutput_Zp.sh = Wrapper for running locally, taking at least 7 arguments:

1. Output directory
2. Year (also "all")
3. Run data
4. Run bkg MC
5. Run signal MC
6. Run BFF signal MC
7. Run specific sample (also "all" and should agree with the previous 4 flags)
8. Run variations (check doAll_Zp function definition for details)

• utils/condor/create_package.sh = Script to package the working directory into a tarball to be sent to condor nodes.

• utils/condor/test_package.sh = Script to test the packaged locally.

• utils/condor/runOutput_Zp_onCondor.sh = Wrapper for running on condor, creating the tarball file and the needed output directories, then submitting the condor jobs. It takes 1 argument:

1. Name of output directory

• utils/condor/runOutput_Zp_onCondor.sub = Condor submit file, including the list of jobs to be run (arguments for the cpp/runOutput_Zp.sh script).

• utils/condor/condor_executable.sh = Script to be run on the condor nodes.

IMPORTANT NOTES:

• The scripts above use the CMSSW_BASE environmental variable, so it is important to have cmsenved in the CMSSW area under the ZPrime directory.
• For submitting the jobs on condor, the x509userproxy needs to have been set. Please export X509_USER_PROXY=/absolute/path/to/proxy/location before running.

---

Additionally, the option to run two more uncertainties was added:

• Muon momentum resolution
• Unclustered energy