feat!: Support Frame Chunking for tasks

[Ahuge]

What was the problem/requirement? (What/Why)

There can be a high overhead for launching AfterEffects (aerender) for each frame and for short renders, this overhead can be more than half of the entire render time for the job.

What was the solution? (How)

This solution uses a clever taskParameterDefinitions range function to implement frame chunking from the OpenJD-Specifications wiki: Search for FrameEndMinusOne

"taskParameterDefinitions": [
                {
                    "name": "FrameChunkStart",
                    "type": "INT",
                    "range": "{{Param.FrameStart}}-{{Param.FrameEnd}}:{{Param.ChunkSize}}"
                },
                {
                    "name": "FrameChunkEnd",
                    "type": "INT",
                    "range": "{{Param.FrameStartPlusChunkSizeMinusOne}}-{{Param.FrameEndMinusOne}}:{{Param.ChunkSize}},{{Param.FrameEnd}}"
                }
            ],
            "combination": "(FrameChunkStart, FrameChunkEnd)"

What is the impact of this change?

A new UI field Frames Per Task in Job-Specific Settings

That field now controls the chunk size for each task.
This modifies the JobTemplate parameters with two new "calculated" parameters FrameStartPlusChunkSizeMinusOne and FrameEndMinusOne which are calculated in the submitter and passed as parameters to the template.

How was this change tested?

We ran jobs through the three Comp Submission workflows: "Submit One Comp", "Submit Entire Queue As One Job", "Submit Entire Queue As Separate Jobs".

Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.

Was this change documented?

Is this a breaking change?

Yes

Runtime Data

I have some runtime metrics from a naive aerender (1 frame per task) workflow and a chunked aerender workflow:

Naive Submission:

 ==== SUMMARY ====

Session Count: 38
Session Total Duration: 0:16:51.511000
Session Action Count: 203
Session Action Total Duration: 0:15:12.578000
Task Run Count: 51
Task Run Total Duration: 0:14:54.141000 (88.4%)
Non-Task Run Count: 152
Non-Task Run Total Duration: 0:00:18.437000 (1.8%)
Sync Job Attachments Count: 0
Sync Job Attachments Total Duration: 0:00:00 (0.0%)
Env Action Count: 152
Env Action Total Duration: 0:00:18.437000 (1.8%)

Within-session Overhead Duration: 0:01:38.933000 (9.8%)
Within-session Overhead Duration Per Action: 0:00:00.487355

My Chunked Submission:

 ==== SUMMARY ====

Session Count: 3
Session Total Duration: 0:01:41.469000
Session Action Count: 15
Session Action Total Duration: 0:01:03.091000
Task Run Count: 3
Task Run Total Duration: 0:01:01.705000 (60.8%)
Non-Task Run Count: 12
Non-Task Run Total Duration: 0:00:01.386000 (1.4%)
Sync Job Attachments Count: 0
Sync Job Attachments Total Duration: 0:00:00 (0.0%)
Env Action Count: 12
Env Action Total Duration: 0:00:01.386000 (1.4%)

Within-session Overhead Duration: 0:00:38.378000 (37.8%)
Within-session Overhead Duration Per Action: 0:00:02.558533

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[sonarqubecloud]

Quality Gate failed

Failed conditions
14.1% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[eherozhao]

This seems out of the scope of this PR. Could we only have Chunking change in this PR?