AY-979 Finalize updating Resolve to new publisher

[robin-ynput]

Changelog Description

Finishes up with Resolve switch to new Publisher.
Finishes up the features that were already implemented in ynput/ayon-core#157

• - @BigRoy suggested warning message if there is not anything to be used for creation
• - @BigRoy flagged that when clicking Create for Create Publishable Clip but there's no valid clips in timeline nothing happens
• - @BigRoy flagged that previous creators was creating instances with invalid folder path(s)
• - @BigRoy flagged issues when deleting instances in the creator
• - Spliting product types into:
  - primary: shot - instance with hierarchy, future context data and attributes placeholder
  - secondary: plate, audio, review - instance with media
• - Hierarchy and context data should be linked from Shot instance for all secondary product types Traypublisher (TP)
• - Each secondary product type which will be created from a clip should have own creator class - like in TP
• - When possible OTIO export should be done via native function rather then our implementation
• - OTIO support for opentimelineio >= 0.16.0
• - Ensure that audio cannot be exported from non-audio timeline(s)
• - Test out with Resolve 19
• - Help description in "?" button
• - Fix review product not published when review_track contains a space
• - Update client/README documentation

Testing notes:

In Resolve:

1. Create a timeline with clips associated to a media
2. (Optional) Make a selection coloring some clips in Chocolate color
3. From Workspace -> Script -> AYON Menu
4. Create and publish product(s) of type shot, audio, plate and review from there

Tested locally on Windows with Resolve 19.0, 18.5 and OpenTimelineIO 0.17.0, 0.16.0.

[ynbot]

Task linked: OP-8066 Resolve: update to new publisher

[robin-ynput]

@jakubjezek001 I've addressed your feedback regarding the has_promised_context. Thanks for that.

Regarding your question about handles workflow.
So, I have never been an editor myself and always was on the tooling side, but I don't recall any dynamic/min handles workflow.
As far as I can remember, Editors were creating shots in Ftrack/Shotgrid with handles defined from client specs document and keep it consistent per shot.
So the logic we have in extract_otio_review (extra from media if available or generate black frames otherwise) is what I am more used to.

[jakubjezek001]

All works fine as expected! Great work @robin-ynput - we can merge this but lets wait also for the merge of ynput/ayon-core#916 and ideally after it is released, so we could change the dependent core version in ayon-resolve\package.py under ayon_required_addons.

[robin-ynput]

DONE:

• Deploy and release Fix wrong retimed detection on image sequence clip. ayon-core#897
• Adjust package.py requirement accordingly
• Merge Transfer editorial package to new publisher #36

[jakubjezek001]

It looks like the linked issue might have been added by mistake. Is it correct? After a quick look at the changes, it seems that the suggested changes from issue #2 weren't applied.

[robin-ynput]

It looks like the linked issue might have been added by mistake. Is it correct? After a quick look at the changes, it seems that the suggested changes from issue #2 weren't applied.

This is not a mistake, I've tested all of the work on Windows with OTIO 0.17.0 and 0.16.0 it works.
I'll do other attempt with 0.15.0 and 0.13.0 to be 200% sure.

So the issue described on this issue has been fixed but with another approach than the suggested change on the ticket (wrapper function + enforce documentation so people use 0.15.0 version).

EDIT: confirmed it works with 0.17.0, 0.16.0, 0.15.0, 0.14.0 and 0.13.0