Chore: Per project bundle

[iLLiCiTiT]

Changelog Description

Adding support for per project bundles.

Additional info

Core addon is aware of per project bundles and is capable of handling them. Addons manager is discovering correct addons based on project and project bundle, CLI functionality handles --project argument with it's value if called command does snot expect project argument to be filled.

Testing notes:

1. Per project bundles should work when combined with Chore: Per project bundles ayon-launcher#238 .

[antirotor]

I am not sure where exactly report issues (launcher or core) but I'll post this one here:

At first, it looks like it is resolving the bundle fine:

this will however spawn another process that has it wrong:

[iLLiCiTiT]

And what you did? Which process you've spawned and how?

[antirotor]

And what you did? Which process you've spawned and how?
This happens when you run

.\manage.ps1 run --project TestProejct

First, it will print correct bundles, than it opens new terminal window and print the other output

[antirotor]

So this is what we found out during testing:

• whenever there is process that cannot be run in the context of project bundle, it should state so (log some message) before running another process in studio bundle context
• web actions are not respecting project bundle settings (tray publisher)
• when you run ayon_console with project bundle set, any new project will use just ayon process (so new console window won't open)

[iLLiCiTiT]

whenever there is process that cannot be run in the context of project bundle, it should state so (log some message) before running another process in studio bundle context

Added log to tray logic causing this.

web actions are not respecting project bundle settings (tray publisher)

Should be fixed now.

when you run ayon_console with project bundle set, any new project will use just ayon process (so new console window won't open)

I think it is not related to this PR. There is upcoming PR here that might fix it, but I'd rather test it together when this is merged.

[antirotor]

and it works!

[antirotor]

this could use typehints 🤖