[UI] Implement a simpler IO routing view while keeping the advanced one

[niklasarnitz]

The current IO routing is powerful, but it exposes too much of the internal FPGA/DSP structure.
That makes sense technically and is great for power users, but it is hard to use for sound techs who are used to Allen & Heath, DiGiCo, Yamaha, etc. and not software developers.

In my opinion we should keep the advanced routing capabilities, but add a more familiar patching workflow on top.

My Idea

Add simpler routing views:

• Input Patch
  • Channel / Aux input receives from Local XLR, AES50, Card/USB, etc.
  • Example: CH 01 <- Local XLR 1
• Output Patch
  • XLR Out, Aux Out, AES50 Out, Card Out, Ultranet
  • Sources grouped as Main, Mixbus, Matrix, Direct Out, Monitor, FX, Talkback, etc.
• Recording / Direct Outs
  • Easy patching from channels/direct outs to Card/AES50/USB
• Advanced Matrix
  • Keep the current full FPGA/DSP routing here for advanced users

UX changes

• Avoid visible terms like FPGA, DSP In, DSP Out in the normal workflow
• Use console-style names: Input Patch, Output Patch, Direct Out, Tap Point
• Show routes consistently as Destination <- Source or Source -> Destination
• Add common block actions like:
  • Patch 1:1
  • Apply to 8
  • Clear block
  • Copy block