Upgrade View and Work range scripting functions precision from float to double

The view and work range scripting functions use float values for their seconds, which leads to precision issues, as these values are stored as doubles. 

Repro:

1. Create a level sequence
2. Run the attached python script

EXPECTED: The view and working ranges don't have asterisks, indicating that the view and work ranges are on integer frames rather than subframes.

Original repro:

1. Create a script that calls Set Work Range Start, Set Work Range End, Set View Range Start and Set View Range End with the values retrieved from the playback start and end times on a sequence
2. Run the script and notice that the view and work range frame numbers have asterisks signifying sub frame timing.
3. Adjust these values from the UI and see how they snap to frames without asterisks 

RESULT

The scripting calls cannot accurately set the view and work ranges