fix: Prevent Nuke from opening multiple submitter dialogs

[jlangmann-aws]

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

Issue: Bea-15149
Previously, a user could open multiple submitter dialogs. The user should not be able to open more than 1 submitter dialog.

What was the solution? (How)

If the submitter dialog is already open, refresh the dialog properties (including job attachments).

What is the impact of this change?

Better user experience

How was this change tested?

Job Bundle Output tests were successful

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

Yes, ran tests. Also tested adding/removing read node dependencies and re-opening the Submitter dialog.

Required: paste the contents of job_bundle_output_tests/test-job-bundle-results.txt here

only diff was my Nuke version (I'm using 14v5)

Was this change documented?

Is this a breaking change?

This change is dependent on - aws-deadline/deadline-cloud#35

[mwiebe]

I think we'll want render_settings to be part of this refresh as well. If we're refreshing an existing dialog, it may be necessary to move the job_bundle_callback out of this function to no longer be a closure. This is because after updating this, the callback is still a closure to the first call that created the dialog, not any of the later updates.

[jlangmann-aws]

Makes sense, happy to do this while I'm at it. It will also be a slightly larger change in deadline-cloud since we'll need to add refresh functions for the Shared Job Settings and the Job Specific Settings UIs.

[jlangmann-aws]

Updated this and the deadline-cloud PR so we're now passing in the render settings. It looks like the job_bundle_callback is valid as is since we're passing in the settings (which are reset if necessary) when submitting a job or saving a bundle.

Also I see that the test coverage went slightly low with python 3.10. I can merge in this PR after Ting's review #18 is complete!