Color Space inconsistency

### Custom Node Testing

- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Expected Behavior

The colors displayed in ALL the image visualizations in ComfyUI should be the same.

### Actual Behavior

However some nodes, do not do color correction based on the color spae of the image file, and so the colors are wrong. Some nodes as the Load Image node works fine, and displays the colors fine. But other like the preview Image node fail at managing the color and display an sRGB version of the image.

https://imgur.com/a/LKemFE4

### Steps to Reproduce

1. Find an image file with color space adobe RGB (1988) (the issue may happen with other color spaces, but that's the one we confirmed). The image should have "extreme" colors, out of the normal sRGB range, or you won't see a difference. Or you can use this one: https://www.persnicketyprints.com/wp-content/uploads/2019/09/AdobeRGB_colorprofile2-1024x660.jpg
2. Use a Load Image node to load the image.
3. Connect the output of the Load image node to a Preview Image node.
4 Run it.
5. You should be able to see the colors are different, not much, but obviously different. Like here: https://imgur.com/a/LKemFE4

### Debug Logs

```powershell
There is no code error here, it's just incomplete implementation or standards or something...

[ComfyUI-Manager] All startup tasks have been completed.
got prompt
Prompt executed in 0.12 seconds
got prompt
Prompt executed in 0.12 seconds
got prompt
Prompt executed in 0.20 seconds
got prompt
Prompt executed in 0.01 seconds
got prompt
Prompt executed in 0.03 seconds
```

### Other

This is a problem specially in professional environments where we work with image files with embedded color spaces, like adobe RGB (1998).

Also, a Comparer node won't work for this because it's the same image, what changes is the representation of color.

And yes, we tried with all the custom nodes disabled in a new comfyui.