fixed  mapping qualities in bug in post processor

Prior to this commit the post processor took 33 from the
BamAlignment.MapQuality score, thinking it was a char
representing  a phred score (like the BQs). In fact, the
MQ in an int, and this causing low-quality reads to overflow
'0' in the unsifned int