Maya: better handling of legacy review subsets names

[kalisp]

Brief description

Multiple reviews from a Maya workfile are blocked by legacy subset names without variant. These names could be used in later process so we cannot replace them, see #424 (comment).

Description

Legacy subset name ({task}Review}) is queried for presence in DB for published asset. If at least one subset found, subset name is kept (which limits possibility of multiple reviews), in other case proper from Creator (which could be configured by
Validator to check uniqueness of subset names was added to catch multiple reviews with legacy name.

Solves #3034

Testing notes:

Test A
0. Before pulling this PR create camera and Review instance in Maya and publish

1. Create at least 2 cameras in Maya
2. create for them 'Review' instances
3. Publish
4. It should fail on Validation

Test B
0. Use different asset then in Test A

1. Create at least 2 cameras in Maya
2. create for them 'Review' instances
3. 3. Publish
4. It shouldnt fail on Validation

[ynbot]

Task linked: OP-3068 Cannot publish multiple review subsets in Maya

[m-u-r-p-h-y]

multiple reviews work as expected

now we should have a look at the broken arbitrary attributes of the review instance