feat: add ability to configure timeouts in submission UI

[AWS-Samuel]

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

There was no mechanism to set timeouts for session/environment actions through the submitter.

What was the solution? (How)

Add the UI. The default looks like the following:

• Use Timeouts is a sticky setting
• The values of each timeout type are a sticky setting

A warning pops up when deselecting the Use Timeouts checkbox

Zero-valued timeouts are not valid, and are highlighted red to help with identification

• On submission the following error pops up for zero-valued timeouts
  

The timeout fields are disabled when the Use Timeouts checkbox is not selected

• Additionally, the zero-value validation is disabled when this checkbox is deselected

What is the impact of this change?

Users can set timeouts in their job and have the corresponding action timeout when the duration has elapsed.

How was this change tested?

• UI was manually tested
• Submitted a job using these changes and confirmed that the job timed out accordingly

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

Yes, I updated the job bundle output test job templates as the default value for the timeout fields has changed the expected template

Timestamp: 2024-05-14T11:54:56.189556-05:00
Running job bundle output test: C:\Users\samcan\git\deadline\deadline-cloud-for-nuke\job_bundle_output_tests\cwd-path

cwd-path
Test succeeded

Timestamp: 2024-05-14T11:54:58.856255-05:00
Running job bundle output test: C:\Users\samcan\git\deadline\deadline-cloud-for-nuke\job_bundle_output_tests\group-read

group-read
Test succeeded

Timestamp: 2024-05-14T11:54:59.780206-05:00
Running job bundle output test: C:\Users\samcan\git\deadline\deadline-cloud-for-nuke\job_bundle_output_tests\multi-load-save

multi-load-save
Test succeeded

Timestamp: 2024-05-14T11:55:01.078336-05:00
Running job bundle output test: C:\Users\samcan\git\deadline\deadline-cloud-for-nuke\job_bundle_output_tests\noise-saver

noise-saver
Test succeeded

Timestamp: 2024-05-14T11:55:02.101071-05:00
Running job bundle output test: C:\Users\samcan\git\deadline\deadline-cloud-for-nuke\job_bundle_output_tests\ocio

ocio
Test succeeded

All tests passed, ran 5 total.
Timestamp: 2024-05-14T11:55:06.716752-05:00

Was this change documented?

Yes

Is this a breaking change?

No

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

[AWS-Samuel]

diff since last review: https://github.com/aws-deadline/deadline-cloud-for-nuke/compare/baecba26110980f121ced862c971c654f9a81cb7..183e7b96a36e258187c0b60ce4f64043b5af1b44

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud