Fix 0 fps

[O-Minor]

The list of valid FPS values had allocated 11 elements but 1 element was not used so it was auto filled with the value 0, allowing 0 fps as a valid value.

Tests: Added tests for value that rounds to 0, 0 itself, and negative value that rounds to zero inside the test that checks for correct rounding, correct value for all of these should be the value a little under 24.

Fix: Changed number of elements of the list from 11 to 10 to get rid of the hidden 0 entry.

All tests passed in the CI.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.52%. Comparing base (8ab0cf9) to head (e5f6915).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2054   +/-   ##
=======================================
  Coverage   83.52%   83.52%           
=======================================
  Files         182      182           
  Lines       13533    13533           
  Branches     1255     1255           
=======================================
  Hits        11303    11303           
  Misses       2057     2057           
  Partials      173      173           

Flag	Coverage Δ
py-unittests	83.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/opentime/rationalTime.cpp	84.76% <ø> (ø)
tests/test_opentime.py	99.75% <ø> (ø)

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ab0cf9...e5f6915. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.