Added byte range check to ODIDDataSource.preroll_static_resource()

Added a check to ensure the effective byte range end is after the
 effective byte range start for a TimeSeekRange lookup.

Issue was revealed testing with a content index file containing
 offsets that were beyond the file length - causing a memory
 allocation error in the ODIDDataSource. Confirmed that this
 condition now causes preroll() to throw an exception instead
 of a memory allocation error.