feat: add Nuke plugin sync

[npmacl]

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

We are working on adding a plugin sync feature, that allows customers to add plugins for the DCCs that will run on deadline cloud workers just by placing the plugins in the correct location in their job attachments bucket.

Also some minor changes in other samples for consistency.

What was the solution? (How)

Copied the existing examples, with some small modifications to be appropriate for nuke. The main change is that the activate script updates NUKE_PATH with the location of the plugin directory (intended to pick up individual .gizmo files), as well as the paths to the init.py files of multi-file plugins.

What is the impact of this change?

sample is updated with the plugin script.

How was this change tested?

Tested with one gizmo and one plugin. For the gizmo I used cp_antialiasing, and for the plugin I used the free version of NNFlowVector.

I installed these locally and created a .nk scene that used both. I tested submitting this to a deadline-cloud SMF farm using the deadline-cloud channel, and got an error related to the plugin being unrecognized.

I then built this sample to my own s3 conda channel, added a queue-environment that set the value of DEADLINE_JA_S3_BUCKET and DEADLINE_JA_ROOT_PREFIX, and uploaded the plugin & gizmo to my job attachment bucket. The directory structure in my bucket was the following:

s3://job-attachments-bucket/DeadlineCloud/plugins/linux/nuke/17.0/
├── CPAntialiasing.gizmo                                                            
└── NNFlowVector-v3.0.1_Nuke17.0_CPU_Linux/
    ├── init.py                             
    └── (other files)

I then resubmitted the job to my queue, but switched to using my s3 conda channel instead of the deadline-cloud channel. This time the job ran successfully. I downloaded the rendered output and compared it to what I rendered locally, and visually the output matched.

Was this change documented?

yes

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

[kenyrish-amazon]

Thanks for making the changes to Maya/Blender recipes! Left a few comments

[godobyte]

Are these env vars used anywhere?

[leongdl]

Not used, and unset at line 61 above. This file is totally optional. I imagine AE being the only one we should clean up.