Split Nuke callbacks defined by `NukeHost` and rework nuke startup

[rdelillo]

Is there an existing issue for this?

• I have searched the existing issues and added correct labels.

Description

Current Behavior

Current behavior make Nuke setup some callbacks and operations through NukeHost when Nuke start in UI mode:

• https://github.com/ynput/ayon-nuke/blob/develop/client/ayon_nuke/api/pipeline.py#L159
• https://github.com/ynput/ayon-nuke/blob/develop/client/ayon_nuke/api/lib.py#L2478

These operations affects colorspace setup, resolution, frame-range...

Expected Behavior

We need to triage those operations between:

• those who can happen on the farm (non-GUI mode) and those who are user-specific
• those we want to happen at nuke start-up and those which need to be re-applied on each workfile opening
• those who are mandatory and those we want to make optional and configured via settings
• those who happens silently vs those who require user confirmation

Once this is done, we'd need to rework NukeHost for this.

Some work was already discussed :

• Split UI and none-UI callback entry point: Ensure Nuke host get installed in terminal mode. #206
• Disable callbacks via plugin settings: Added setting for disabling forcing context settings #193

Steps To Reproduce:

No response

Additional context:

Version

Version of the server, ayon-core and the addon that's affected

What platform were you running when you found the bug?

Windows
Linux - Rocky9
Linux - Ubuntu
MacOS

You can also provide any additional information relevant to the issue.

Relevant log output: