Implementation of custom frame range collector

[moonyuet]

Changelog Description

This PR is to implement the custom frame range collector with the custom frame range migrated from deadline addon.

Additional info

Tested with ynput/ayon-deadline#252

Testing notes:

1. Create Render
2. Test with both local and farm rendering.
3. Test with or without custom frame range

[Copilot]

Pull request overview

Implements a new Pyblish collector in ayon-core to expose and collect an artist-configurable “custom frame range” for render submissions (migrated from the Deadline addon behavior), storing the selected frame expression into instance data for downstream submission logic.

Changes:

• Added CollectCustomFrameRange instance plugin to provide publish attributes (use_custom_frames, frames) and collect them into instance.data.
• Added create-context value-change callback to refresh the attribute definitions when relevant values change.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[BigRoy]

Ouch, this is painful. We'll need to define a better way to when this plug-in should be relevant.

@iLLiCiTiT let's discuss when we can find some time.

[iLLiCiTiT]

Yep you're right. This might the breakpoint for me. We will have to tackle the "families" thing.

[LiborBatek]

Works for me together with ayon-3dsmax and ayon-deadline with related branches...

[iLLiCiTiT]

Currently shows the attribute at places where it should not be visible. Has to be resolved first (connected to #1818 (comment) )

[antirotor]

So is there any follow-up issue somewhere? I guess it is bigger topic with families and all, but it shouldn't hold up resolution of this? If it works, lets merge it, but create the issue to fix the families?

[iLLiCiTiT]

If it works, lets merge it, but create the issue to fix the families?

It works where it is needed, and it breaks places where it should not be used. So yes, it does resolve the issue, but creates multiple other issues.

[BigRoy]

So yes, it does resolve the issue, but creates multiple other issues.

Let's describe the new issues it creates - track them by priority and resolve the ones we absolutely must and then get to making tickets for those that can be fixed later please.