Fix wrong retimed detection on image sequence clip.

[robin-ynput]

Changelog Description

This PR addresses the bug described on #895 regarding retiming OTIO clip from image sequence.

• Need to conform source_range to available_range rate
• Retiming logic was when input media does not start 0 (image sequence, metadata...)
• Ensure embedded TC are treated correctly
• Need to preserve accurate discreet frame number when dealing with img sequences

Testing notes:

Environment prep

1. copy paste items form both tool.poetry.dependencies and ayon.runtimeDependencies sections from ayon-core\client\pyproject.toml into root level pyproject.toml under tool.poetry.dev-dependencies
2. remove ayon-core\poetry.lock
3. run .\tools\manage.ps1 create-env (windows)

Your .poetry and .venv should be installed in root of repository

Testing

1. Run the unit tests
   run .\tools\manage.ps1 run pytest .\tests\client\ayon_core\pipeline\editorial\ (windows)

AY-979

[jakubjezek001]

For the testing data, we also need to check the retime effects (LinearTimeWarp, FreezeFrame, TimeEffect). Since the method name relates to retiming, this will cover the full range of functions. Great job on practically developing the unittest we really need! I'm thinking about whether we should add the test to the appropriate folder. @kalisp and @antirotor could lend a hand here, especially since ayon-core doesn't have a test folder yet.

[jakubjezek001]

Before the introduction of Resolve's native OTIO, we mainly relied on two attributes:

• The clip's source start frame as a relative range to the available media range.
• The clip's media range as an absolute range, including the metadata timecode value.

With Resolve's interpretation of OTIO now in play, we consider:

• The clip's source start frame refers to a trimmed absolute range that is available.
• The media range remains absolute, including metadata.

We reference the media source to an absolute value with included metadata because of FFMPEG. Since we use FFMPEG for video trimming, it's crucial to have the timecode correctly defined.

First, figure out if the clip source range is relative or absolute to the media range. Next, find the relative source frame value and continue as before, making sure to clear up any confusing code that's mistakenly referring to me (old me 😄).

[antirotor]

... especially since ayon-core doesn't have a test folder yet.

but it can - I added one for my own tests, see feature/OP-1188_better-representation-model branch.

[iLLiCiTiT]

Code looks ok. @jakubjezek001 merge if is ready please.

[jakubjezek001]

Tests in Hiero didn't go well.

[jakubjezek001]

Fantastic work @robin-ynput ! Thanks a lot! 💫 💥