[Bug]: 10bit OpenGL Output Broken

### What happened?

Today I built OpenRV 3.1.0 from source and had to discover that 10 bit output via OpenGL does not work. I am running 3 displays, one of them is 8bit+frc connected via displayport and configured for 10bit output in the Nvidia driver.
The next one is true 10 bit, also connected via displayport and also set to 10 bit in the Nvidia Control Panel.
The last is also true 10 bit, connected to a Blackmagic Decklink mini monitor 4k. GPU is an RTX 4090 running the latest studio driver (581.29), OS is Win11 24H2.
I built two versions of OpenRV 3.1.0, one with and one without the Blackmagic SDK. 10 bit via the GPU doesn't work with either build. 10 bit via the Decklink card works just fine. Toggling the "Video Sync" option also results in the same error: "Display Configuration is invalid"

_I also checked again with OpenRV 2.2.0, which I have been using for the longest time now and there 10 bit output works perfectly fine for all connected displays._
EDIT: After going back and forth and testing some more it seems that now in RV 2.2.0 10bit isn't working either for the displays attached to the GPU and I'm seriously starting to question myself if it ever worked or if dreamed that or mixed it up with the dithering options....

Can anyone confirm that this is a general bug and not just a problem on my end? Is there something I can try to do about it myself?

If you need any further info, please let me know!

All the best

Janis

### List all the operating systems versions where this is happening

Windows 11

### On what computer hardware is this happening?

RTX4090, AMD 7950x3D, 16 cores, 128GB ram

### Relevant console log output

```shell

```

### Environment variables

_No response_

### Extra information

_No response_

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start by reproducing the report on Windows 11 with the listed RTX 4090, multi-display 10-bit configuration, and OpenRV 3.1.0 build variants. No source file, test, or entry point is named; use the “Display Configuration is invalid” result and compare GPU output with the working DeckLink path. Done means the 10-bit GPU output configuration works or the failure is clearly documented with a confirmed cause.

Written by the indexing model from the issue text.