Testing of 'implausibly' small or large mchirp point estimates

While we think that mchirp < 0.1 or mchirp > 1000 is not going to happen, based on the known search boundaries, there may be instances of unexpected / buggy pipeline behaviour where not 100% of probability lies within the existing bins.

I think we would like the code to not crash/error in this case, but possibly to throw some sort of warning so that a person could be alerted to investigate. I don't have any concrete suggestion for how to do that atm, maybe by applying a special label. (Along the lines of HIGH_PROFILE ... eg MCHIRP_PROBABILITY_LT_1).

To begin it would be good to have test cases where we know that some probability will be outside the 0.1-1000 range.