Fix to ODIDDataSource MP4 processing to not trim/touch the MP4 for full-range time-seek request (fix for CVP2RI-384 and CVP2RI-387)

Simplified the ODIDDataSource.preroll() to call preroll_mp4_resource() for
 all cases where resource_has_mp4_container() is true. (renamed
 from preroll_mp4_time_seek())

ODIDDataSource.preroll_mp4_resource() changes:

 Now throws if the request includes a PlaySpeed or a DTCPCleartextRequest.

 If no seek request is included or a ByteSeek is included, it delegates to
  preroll_static_resource ().

 Most importantly, if the TimeSeekRange is from 0 to end,
 IsoFileContainer.trim_to_time_range() is not called and the TimeSeekRange
 response will include the content duration and source content size. (note
 that this tests the integrity of the serialized IsoFileContainer since the
 TSR response range and Content-Length response header data is based on the
 raw file length but streaming is from the IsoFileContainer representation)

Fixed up a bunch of references to ODIDDataSource memvars without "this."
 prefix.

Tested with MP4 TimeSeekRange requests with 0- ranges and closed data
 ranges and various Range requests using
 bbb_avc-main_720x576i50_2M_heaac51_48kHz_160kbps.mp4.

Found a problem with open range requests with non-0 npt start times. Will
 file a separate bug/fix for the issue.