Enhancement: Outdated containers dialog optional and shortcut to manage

[Tilix4]

Changelog Description

Change Harmony warning dialog when there are outdated containers in scene to a python Qt one with a button to directly open Manage. Also add a setting to disable it.

Additional review information

Disabling it might be useful when you want to automate operations on workfiles in UI mode with Harmony. For example, if you want to run a script to actually automatically update the containers, the existing dialog will block you.
The new Manage button makes easier for the artist to deal with outdated containers.

Testing notes:

1. Open Harmony scene with outadated containers

[iLLiCiTiT]

I would move this to pipeline.py. It is the only place using this function, and I can't imagine being used elsewhere.

[BigRoy]

Disabling it might be useful when you want to automate operations on workfiles in UI mode with Harmony. For example, if you want to run a script to actually automatically update the containers, the existing dialog will block you.
The new Manage button makes easier for the artist to deal with outdated containers.

To me a 'setting' doesn't sound like the best fix for that. Because you may want your regular production to get the validation, but your automation not to. Sounds more like you'd need something like if is_automation(): to then skip the validation.

Similar to how we'd do a headless check in many DCCs to skip validating/showing the dialog then here we'd maybe also skip on if the session is explicitly marked as running in some 'automation' mode. Which could just be an env var really?

[Tilix4]

Which could just be an env var really?

That was my first lead, but I didn't want to introduce a new dedicated env var which is not really headless but not fully UI... and as you can run your automation under different settings than the production, I thought it'd fit.
If you agree on an env var name I'll go for it.

[iLLiCiTiT]

Related to automations, could that be just check of is_headless_mode_enabled from ayon core?

[Tilix4]

Related to automations, could that be just check of is_headless_mode_enabled from ayon core?

I'm not sure about what this mode covers exactly, but if it is running DCCs without GUI, therefore it'll be very restricted. Harmony's CLI is limited and we may want to process automated operations in GUI (using ayon-launch-scripts for example), this is why this pop-up is blocking in this case.

[iLLiCiTiT]

Harmony's CLI is limited and we may want to process automated operations in GUI (using ayon-launch-scripts for example), this is why this pop-up is blocking in this case.

The point is that it should not show UI in headless mode, which is usually used for automations.

[Tilix4]

The point is that it should not show UI in headless mode, which is usually used for automations.

So I think we cannot rely on this for contextually disabling this pop-up to fit my use case

[iLLiCiTiT]

So I think we cannot rely on this for contextually disabling this pop-up to fit my use case

Ok, but it still should be checked...