Handle EVDI Formats

We need to implement better "mode" handling and format handling from EVDI. Not sure how much work is involved here, may just be primarily investigation.

Answer these questions:
- What are EVDI "modes"? How do they relate to actual monitor behavior? (since EVDI is a simulated monitor)
- How would a potential Windows driver represent these same modes, if at all? Or are they OS-specific?
- How will these modes correspond to an encoder? For instance, when implementing H.265, what of these "modes" will matter to the encoder?
- Will the client influence these modes at all, even though we are transporting over some sort of transport? Or should we just settle on a "best mode" for transporting over some low-latency transport?

Feel free to ask @Copilot or some other AI, but we *should not* generate code for this (or much of anything). The goal is to understand the problem.

Investigate EVDI (a virtual display interface for Linux) to understand its mode and format handling. Determine how modes relate to simulated monitor behavior, cross-OS implications, encoder interactions (like H.265), and client influence over transport. Start by reading EVDI documentation and existing code in the repository that interfaces with display handling.

Scritto dal modello di indicizzazione a partire dal testo della issue.