Bugfix/houdini: wrong frame calculation with handles

[MustafaJafar]

Changelog Description

This PR make collect plugins to consider handleStart and handleEnd when collecting frame range
it affects three parts:

1. get frame range in collect plugins
2. expected file in render plugins
3. submit houdini job deadline plugin

Testing notes:

1. create a render instance
2. publish
3. check render job meta data

[ynbot]

Task linked: OP-6806 Houdini: wrong frame calculation with handles

[MustafaJafar]

as @moonyuet said, if OP wants to control the extraction of files as well (caches and rendering) this validation would probably be more annoying than helpful, there's many different cases you want full control of the rop range you are generating and on the cases you'd want the full range you'd just leave the default of $FSTART and $FEND so the pipeline that already updates the scene frame range handles those cases...

I don't meant to control the frame range.
I think the validator is working correctly by the logged message is wrong.

if users didn't turn off and added their custom frame range without considering start and end handles then
frameStart may have a greater value than frameEnd

do you have any suggestion how to explain that in log.error ?

---

Also, There's BigRoy's suggestion:
Adding handleStart and handleEnd attributes on the instances (initialized with 0) then the toggle on the collector will switch between asset handles and instance handles

[BigRoy]

Didn't test it.
Code looks good - only had some cosmetics comments on a docstring.

[moonyuet]

Looks good for me in the simple testing.

[BigRoy]

@antirotor ready to merge?

[mkolar]

All good. thanks.