fix: Update frame range when write node is selected

[diane-hj]

This is the same PR from #154
The commit was merged in during release window, so got reverted. The PR is to re-merge the changes back.

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

When write node is selected, incorrect frame range were exported in parameters

What was the solution? (How)

• When override frame is selected, override the frame
• When write node is selected with limit_range checked (without override), write node's frame applied
• When write node is selected without limit_range checked (without override), project settings frame applied
• When no specific write node is selected, project settings frame applied

What is the impact of this change?

• Based on the customers' setting, right frame range is selected as explained above

How was this change tested?

• Opened Nuke with the following setting:

Project setting frame: 1-4
Write1 node frame: 1-10
Override when selected with frame: 4

Verified the following:

All write nodes, without frame override —> 1 - 4 
All write nodes, with frame override —> 4 
All write nodes, without frame override —> 1 - 4

Write1, with limitRange, without frame override —> 1 - 10 
Write1, with limitRange, with frame override —> 4
Write1, with limitRange, without frame override —> 1- 10 

Write1, without limitRange, without frame override —> 1- 4
Write1, without limitRange, with frame override —> 4 
Write1, without limitRange, without frame override —> 1 - 4 

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

Timestamp: 2024-08-12T14:01:24.012286-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/group-read

group-read
Test succeeded

Timestamp: 2024-08-12T14:01:25.055533-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/noise-saver

noise-saver
Test succeeded

Timestamp: 2024-08-12T14:01:26.720246-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/multi-load-save

multi-load-save
Test succeeded

Timestamp: 2024-08-12T14:01:27.757395-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/frame

frame
Test succeeded

Timestamp: 2024-08-12T14:01:29.360422-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/ocio

ocio
Test succeeded

Timestamp: 2024-08-12T14:01:30.340508-07:00
Running job bundle output test: /Users/chaejung/Desktop/submitter/deadline-cloud-for-nuke/job_bundle_output_tests/cwd-path

cwd-path
Test succeeded

All tests passed, ran 6 total.
Timestamp: 2024-08-12T14:01:33.469925-07:00

Was this change documented?

No

Is this a breaking change?

This is fix.

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 passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[Cherie-Chen]

Looks great! Thanks for the PR!