[bug] time boundary manager incorrect handling non-overlap realtime/offline table segments

one should use all offline table segments, instead of -1 day if realtime table doesn't exist or there's a gap between the realtime and offline table segments in terms of time overlap-ness

Locate the time boundary manager and inspect how it handles realtime and offline table segments. Reproduce cases where the realtime table is absent or has a time gap with offline segments; done means all applicable offline segments are used instead of defaulting to -1 day.

Written by the indexing model from the issue text.