Fix opus_support.py for new julian library bug fix

[rfrenchseti]

• Fixes #N/A
• Were any Django, import pipeline, or table_schema files modified? Y
  • If YES:
  • Database used (or new import): New import
  • FLAKE8 run on modified code: Y
  • All Django tests pass: Y
  • Code coverage run and still at 100%: Y
• Were any JavaScript or CSS files modified? N
  • If YES:
  • JSHINT run on all affected files: Y/NA
  • Tested on Chrome, Firefox, Safari, Edge, and iOS: Y/NA (Remember to test all browser sizes)
  • Tested for race conditions (with delayed API calls if applicable): Y/NA
• Was the documentation reviewed for necessary changes or additions? Y/NA
  • About
  • Getting Started
  • FAQ
  • API Guide
  • Tooltips
  • Import/database schema

Description of changes:

Adapt OPUS to rms-julian v2.0.0 and later. To test this, you must update your virtual environment with the latest version of rms-julian as specified in requirements.txt.

The major rewrite of the rms-julian package fixes a bug in the zero-point for time, resulting in various test cases needing to be modified. Minor other changes required fixes to opus_support.py as well.

MAJOR NOTE: FROM THIS POINT ON OLD DATABASES ARE NO LONGER COMPATIBLE AND YOU MUST ALWAYS USE A DATABASE THAT WAS IMPORTED AFTER THIS VERSION OF JULIAN WAS RELEASED.

Known problems:

BTW I fixed the old Windows line-ending on opus_support.py so be sure to look at the diffs with Whitespace turned off to see what really changed.

[pds-admin]

My mistake. Let me update the requirements.txt.