[Feature]: Separation of channels & URL query

### Problem to solve

Good stuff.

This isn't as much as a request as it's just some ideas off the top of my head.

Just some ideas to keep you going ;)

Regards,
Toon

### Proposed solution

1) I think it would be cool if you had a separate channel for plotting and for terminal messages.

E.g.: messages starting with 0x00 go to the plotter, messages with 0x01 got to the terminal.

You could even allow multiple channels for plotting and multiple terminal channels. A split screen where the left is the scope and the right is the terminal would also be cool.

Example use case:
Imagine an application with 2 motor's being controlled by 2 pid loops. We could split the uart data into 4 channels:
- 0x00 Plotting of PID internals of motor 1
- 0x01 Terminal to tune PID of motor 1
- 0x02 Plotting of PID internals of motor 2
- 0x03 Terminal to tune PID of motor 3

2) Another cool feature would be if you could "configure" the ui through a url query.
E.g: https://web-serial-plotter.atomic14.com/?legend=p_error,i_error,d_error

That way you could always come back to the same setup.

### Alternatives considered

_No response_

### Area of the app

None

### Willingness to contribute

- [ ] I'd be willing to submit a PR for this
- [ ] I can help test and provide feedback

### Additional context, screenshots or mockups

_No response_

Das Issue nennt keine Dateien, Tests oder konkreten Einstiegspunkte. Beginne damit, den Datenfluss von Web Serial, die Plot- und Terminalansichten sowie die Verarbeitung von URL-Abfragen zu lokalisieren; abgeschlossen wäre die Arbeit erst mit einem abgestimmten Design für die Kanaltrennung und eine reproduzierbare UI-Konfiguration, gefolgt von Tests für beide Funktionen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.