fixed missing stop-time reasons and overlapping limit LBs

When a stop time is found (SB but no run) the app relied on the DB to also contain entries for system and reason for this exact IOV. Unfortunately that is not always the case (one example is found on the 2nd of July 2018) so when placing out the "stop info" a break segmentation fault would be thrown as the system and reasons containers are empty. Fixed it by putting a default value for this (Unknown).

The way this app is used (in the Daq Eff and Splunk environment) makes the app count the same LB twice, the last indexed LB with the first indexed LB in the next application run. A 60 second offset was added in the start time of the indexed time period.