Add the options to enable context and its related settings

[moonyuet]

Changelog Description

This PR is to add the options to enable and its related settings through the addon settings.
Throughout this PR, users can also choose whether enabling to set context settings during callbacks.

Additional review information

Marked it as draft, we need to discuss whether better designs for the setting needed for this.

Testing notes:

1. Launch Nuke
2. Toggle the settings from ayon+settings://nuke/general/settings_to_apply in AYON server

[moonyuet]

@rdelillo @BigRoy I split the callbacks regarding to #211. I know there is another PR #193 which does the same thing on the context setting, and I will merge the changes (mainly for the context setting) once it is merged.

[BigRoy]

Nice! Some small notes left.

[rdelillo]

Approving this one cause it works as expected and it's very convenient to be able to switch callbacks individually like that 💪
Tested on Nuke 17.0, I disabled callbacks on create and enabled on open.

Small Notes:

• Need to fix the lint
• Is it a problem to always register 1 big function as callback that read the settings vs add granular functions as callbacks based on settings ? I don't see any issue and maybe safer for now, but just want to mention it.

[moonyuet]

• Is it a problem to always register 1 big function as callback that read the settings vs add granular functions as callbacks based on settings ? I don't see any issue and maybe safer for now, but just want to mention it.

Not sure if there is any reason behind adding those functions explicitly as callbacks before. But in general(like in other hosts), we added the callback with its related function (new_callback would trigger the on_new function which did workfile template build, set context settings etc.). I think the nuke host should align with what we have done in terms of callback if possible.

[BigRoy]

• Is it a problem to always register 1 big function as callback that read the settings vs add granular functions as callbacks based on settings ? I don't see any issue and maybe safer for now, but just want to mention it.

A problem in which way? I don't really see any issues with it either way. I prefer myself to just register a single thing to the DCC and then keep things in AYON land where we control it our way instead. If any of these ever need to run in a certain order, etc. we then know which order it's running in - if we register them with Nuke, I wouldn't know for example.

[BigRoy]

LGTM - just refactor on_root_load -> on_script_load.