cmsRun returns non-zero if caught unix signal

If any of the signals cmsRun catches (SIGINT and SIGUSR2) are caught, cmsRun now returns a non zero value. This was requested by data ops.
Backported from CMSSW_7_0_X.
Merge pull request #1815 from Dr15Jones/cmsRunReturnNonZeroOnSignalFor4_4_X

Framework fix -- cmsRun returns non-zero if caught unix signal
dbs to das migration
Merge pull request #2423 from vlimant/DBS2DAS-ConfigBuilder-4.4

dbs to das migration in 4.4
fix for --filein das: --filein dbs: options
Merge pull request #2426 from vlimant/DBS2DAS-ConfigBuilder-4.4

fix for --filein das: --filein dbs: options
use the das client attached to the release
Merge pull request #2531 from vlimant/DBS2DAS4Matrix-4.4

use the das client attached to the release in the matrix
Align package 'MuonAnalysis/MomentumScaleCalibration' to CMSSW_5_3_12.
Fix typo which caused the arrow plots to be not produced.
More detailed DMRs (range +-10um, bin width 0.2um).
Align package 'MuonAnalysis/MomentumScaleCalibration' to V00-07-07-01
Use explicit file names instead of pattern matching for removal of unmerged files.
Added check, if merging of parallel output failed.