Added a check for tracks with nDoF>256 into TupleToolTrackInfo

Added a check for tracks with nDoF>256. If such a track appears, ProbChi2 is set to -1.

The reason for this is when using TupleToolTrackInfo for WG TrackCalib production, the following error was occasionally spotted:

TupleMuonTTPlus FATAL Standard std::exception is caught TupleMuonTTPlus ERROR array::at: _n (which is 277) >= Nm (which is 257) We found that the error is triggered by probChi2(). From the information at doxygen http://lhcb-doxygen.web.cern.ch/lhcb-doxygen/davinci/latest/d7/dc6/class_l_h_cb_1_1_track.html#a60eef162cbcc97106e34f860eebb70b6 this is an issue emerging from nDof > 256.

The tracks used for TrackEff studies are MuonTT tracks. The number of muon hits can be rather large, causing nDoF > 256.