🏛️Product base types: Support in Creator logic

[antirotor]

Changelog Description

Add support for product base types to creation logic in ayon-core.

Additional info

This is the first part of gradient transition of product type to optional alias for product base type. To keep the backwards compatibility, product base type is introduced as an optional argument to most of the existing functions. If it is not passed, warning is emitted - this will in most cases comes from the Creator plugins not implementing product base types.

So far - on the data model - product type is mandatory and product base type is nullable field. This will change in the future when product_base_type is consistently used across all the addons out there.

Reflecting product_base_type in product name won't work if creator plugin overrides get_product_name() function. If it does, it needs to be refactored.

Also, the way how Creators create CreatedInstance differs so this must be considered too. The logic goes like this:

If product_base_type is passed to the constructor, it will be used. If not and the creator (it needs to be passed there too) itself defines product_base_type, it will use that one.

There are some questions lingering:

How to handle product_base_type in Anatomy and Product name templates until it is made mandatory? If you have {product[baseType]} token in your templates:

product_type	product_base_type
✔️	❌	use product_type
❌	✔️	use product_base_type
❌	❌	is invalid state
✔️	✔️	use product_base_type

Note

Closes #1297

Warning

This will break Maya integration if ynput/ayon-maya#282 is not resolved and maybe other hosts.

Testing notes:

For more information see description of #1297

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.