Migrate to OIIO3 and build with OCIO

[mcoliver]

OIIO development has moved to v3. Also adding ocio support with oiio.

Linked issues

fixes #893

Summarize your change.

Upgrade OIIO to v3 and build with OCIO

Describe the reason for the change.

OIIO v2 is considered obsolete: https://github.com/AcademySoftwareFoundation/OpenImageIO/releases/tag/v2.5.19.1

Note that this is a patch release for the obsolete 2.5 branch that merely repairs its ability to build under new versions of some dependencies. You need not upgrade if you are not encountering build problems. Except for legacy constraints, everybody should currently be using OIIO 3.0 and testing the beta for 3.1 which will become the new supported branch very soon.

Describe what you have tested and on which operating system.

built locally and tested on macos for 2024 and 2025. Need the Academy's CICD to build for other configs

Add a list of changes, and note any that might need special attention during the review.

It appears OIIO implementation is pretty minimal so I think we should be good but testing on other distros to validate would be appreciated.

If possible, provide screenshots.

[cedrik-fuoco-adsk]

Why did you add this? Is there a missing dependencies? I don't think it should be needed since OCIO version hasn't changed.

[mcoliver]

https://opencolorio.readthedocs.io/en/latest/quick_start/installation.html#automated-installation

MISSING is the default so this line is not needed. I was debugging some things on my local machine (issues specifically with yaml-cpp) and had added the line so I could set it to NONE or ALL. Would recommend leaving it for debugging purposes but also understand not adding unnecessary lines.

I defer to your judgement here on what to do. Please let me know which direction you would like to go with.

[cedrik-fuoco-adsk]

Thank you @mcoliver! I added the do not merge label because we won't merge this before mid-february at the very least. We don't want to change dependencies versions before the incoming release.