Chore: Product name and type

[iLLiCiTiT]

Changelog Description

Goal of this PR is to start using product naming in code base. Which means to use productName and productType instead of subset and family during create and publish phase.

Additional info

First of all I'm 100% sure that I broke something, if you can, please do code review first before you try to run. If you find any issues please report as soon as possible, you can DM me with quick questions.

All changes should support compatibility with workfiles before this PR in all hosts.

All the time when a family did represent product type, it should be changed to product type. e.g. create plugin does have product_type instead of family and created instance has productType in data instead of family.

One of the goals was to also use productType instead of family during publishing and use only families for pyblish filtering. The key family key is filled by pyblish automaticlly to "default", so it should not be an issue. But when we planned it, we didn't realize that sometimes instance.data are filled with raw data from scene, and in that case there might be family with a value that is not managed by us, speaking only about logic or workfiles with instances before this PR. I've changed that idea and all the time productType is changed during publishing, family is changed too.

What I couldn't resolve

1. Json files in Blender and Unreal
   Sometimes it looks like the json is storing data that are unused, and sometimes I couldn't find source of their data so I couldn't tell if/how should I modify them. Sometimes the data are stored unclearly under key that says nothing about the value, e.g. json has "_id" which in fact represents representation id. Some of the json files are storing family which should be probably changed to product_type but I didn't find where the value is used. etc.

2. Json files in Maya
   This is just about looks publishing, needs validation that I didn't break anything.

3. Resolve and Hiero
   I probably failed at backwards compatibility.

Testing notes:

• For host testing go one by one.
• Go through code if you can and scan if you find invalid changes.
• Open host and try all create plugin and publish. Validated output if can be loaded.
• Open the host you're testing with workfile that does have instances before this PR and publish them.
• 3dsMax
• AfterEffects
• Blender
• Fusion
• Hiero
• Houdini
• Maya
• Nuke
• Photoshop
• Resolve
• SubstancePainter
• TrayPublisher - simple creators
• TrayPublisher - editorial
• TVpaint
• Unreal
• Celaction
• Flame
• Harmony

Note: This PR is clashing Hiero integration PR #87

[MustafaJafar]

I tested it in Houdini and it works.
Few notes for reference.
Note 1:
It'd be better to prefix all parameters as you and @BigRoy mentioned here #115 (comment) . I think we can do it in another PR as the current status doesn't conflict with the implemented product types.

Note 2:
I faced few bugs but I think they are not related to this PR as I was able to replicate them in develop branch.

• Publish Image sequence (for some reason, representation data are empty)
• Loading HDAs from Loader (where Loader fetches the wrong version)

[jakubjezek001]

Hiero and Resolve works!

[moonyuet]

Tested in 3dsmax and substance painter. So far so good.

[jakubjezek001]

Traypublisher's Simple EDL editorial works like a charm ;)

[jakubjezek001]

Traypublisher's Simple Creators works too.

[MustafaJafar]

Creator Tab in Publisher tool is able to get the product name correctly.
Thanks.

[simonebarbieri]

Blender and Unreal works. There are a few issues in Unreal, but unrelated to this PR.

[antirotor]

I've hit issue when publishing renders from maya, but it doesn't seem to be connected to this PR. So fo me and Maya 👍🏻