Support merged AOVs in arnold render

[MustafaJafar]

Changelog Description

Fixes #69

Test Runs

Here's a test run on my side.
The setup is shown in the ROP node parameters and the created files are shown in the removed files log.

Testing notes:

1. Create AYON Arnold ROP publish instance.
2. Configure the ROP node to have multiple AOVs and set them to separated files
3. Publish. AOVs with separated files should be a separated publish instance.

[kartikgupta]

Thannks @MustafaJafar and @BigRoy for looking into it.

There are parts of the pull request that I don't understand completely.
Is it trying to support separated AOVs, or combined AOVs?
Looking at the previous comments, the discussion seems to be revolving around how to resolve the aov file paths.

But what we're looking to get is that it shouldn't look for the AOV file paths at all and just integrate the overall file path mentioned in ar_picture attribute of the rop, instead of integrating each AOV.
Not sure if there's something I'm missing here.

[BigRoy]

But what we're looking to get is that it shouldn't look for the AOV file paths at all and just integrate the overall file path mentioned in ar_picture attribute of the rop, instead of integrating each AOV.
Not sure if there's something I'm missing here.

It should do that with the current changes as it would now ignore active AOVs that are not explicitly set to be a separate file.

Is it trying to support separated AOVs, or combined AOVs?

In the comments we're trying to make sure it does both correctly - but the part that allows combined AOVs should already have been solved looking at the code.

Anyway, I'll do some testing.

[kartikgupta]

Thanks @BigRoy for clearing up the misunderstanding!

[BigRoy]

This fixes at least being able render MERGED aovs.

We should follow up with a new issue and PR after this to solve the remaining TODO and the notes given in this comment.

Note that I have not tested whether Cryptomattes break the current "merged" AOV publishing so that remains unconfirmed.