inconsistent return value of ProjDataInfo::get_bin() and CListEvent::get_bin() when out-of-range

ProjDataInfo::get_bin sets bin_value to -1 if the request bin is outside of the allowed range (and says so in the doxygen).

Some derived ClistEvent*::get_bin() sets bin_value=0 if out-of-range, others to -1. (CListEvent`'s doxygen says it will return bin_value<=0, so is also correct).

Luckily LmToProjData::get_bin checks if bin_value<=0 so both options are ok.

Nevertheless, it would be better to be consistent. A value of 0 might make most sense as LmToProjData::get_bin will set it to zero (as it has to be able to return negative numbers to cope with delayeds). This would be inconsistent with ProjDataInfo::get_bin's documentation though so might affect someone.

Search for ProjDataInfo::get_bin and the derived CListEvent::get_bin implementations, then compare their out-of-range return handling with the Doxygen described in the issue. Determine which sentinel value is intended without breaking LmToProjData::get_bin, update the affected implementations and documentation consistently, and verify the behavior across the relevant get_bin callers.