Bug: Pipeline colorspace "compatible_python" function does not correctly detect python version
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior:

The [`compatible_python` function](https://github.com/ynput/OpenPype/blob/82f9da2c8ee4cc1a8062737b8ce3bf99afde73f3/openpype/pipeline/colorspace.py#L240-L245) will currently always return false due to it comparing against `sys.version` which is a string like:
```python
3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)]
```

As such a comparison `sys.version[1] >= 9` does not check whether the minor version is higher or equal to nine.

### Expected Behavior:

Function should likely be:

```python
def compatible_python():
    """Only 3.9 or higher can directly use PyOpenColorIO in ocio_wrapper"""
    compatible = False
    if sys.version_info.major == 3 and sys.version_info.minor >= 9:
        compatible = True
    return compatible
```

### Version

3.15.12-nightly.1

### What platform you are running OpenPype on?

Windows

### Steps To Reproduce:

Run Tray Publisher from code on Windows - you'll briefly see a command prompt show up indicating that it's using the Subprocess route for getting OCIO configs + it's relatively slow.

### Are there any labels you wish to add?

- [X] I have added the relevant labels to the bug report.

### Relevant log output:

_No response_

### Additional context:

So this PR https://github.com/ynput/OpenPype/pull/4901 in Tray Publisher for me introduces quite a slow down on reset with color management enabled in 3.15.11 - Running from code I can visually see a command prompt pop up so it looks like it's still forcing a subprocess (command prompt?) to open to retrieve the colorspaces. My first thought was: shouldn't tray publisher be able to just get it through the OCIO Python API instead? @jakubjezek001 

Running this in the console of OP tray:
```python
import sys
print(sys.version)
import PyOpenColorIO
print(PyOpenColorIO)
```

Gives me:
```
3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)]
<module 'PyOpenColorIO' from 'E:\\\\openpype\\\\OpenPype\\\\.venv\\\\lib\\\\site-packages\\\\PyOpenColorIO.pyd'>
```

So I'd expect it to just go through that in standalone publisher.

Then I noticed this 



[cuID:[OP-6281](https://app.clickup.com/t/861n0787v)]
diff --git a/openpype/pipeline/colorspace.py b/openpype/pipeline/colorspace.py
index 269825f85f..d5f2624155 100644
--- a/openpype/pipeline/colorspace.py
+++ b/openpype/pipeline/colorspace.py
@@ -240,7 +240,7 @@ def get_data_subprocess(config_path, data_type):
 def compatible_python():
     """Only 3.9 or higher can directly use PyOpenColorIO in ocio_wrapper"""
     compatible = False
-    if sys.version[0] == 3 and sys.version[1] >= 9:
+    if sys.version_info.major == 3 and sys.version_info.minor >= 9:
         compatible = True
     return compatible
 
['openpype/pipeline/colorspace.py']