Add output pair knowlege to OutputController / Output

[reinder]

Currently in Traintastic an Output is a single output, but not all digital system do support that, e.g. in the Z21 protocol (see #56) the outputs can't be controlled individually.

For implementing #21 it is required to know if an output is a pair or individual.
If the user enters e.g. turnout address 8 it should use: individual outputs 15 and 16 or output pair 8.

I'd suggest to add a outputType(uint32_t channel) method to the OutputController and a outputType() method to Output.
The method can return an enum OutputType with values: Unknown, Single, Pair.

---

Update 2023-11-04:

Investigate how outputs and adressing works on different systems, see also #21.

Protocol / Command station	Channel	Behavior
DCC++EX	DCC accessory
DCC++EX	Output
DCC++EX	Turnout
ECoS	-
LocoNet	-
Marklin CAN	DCC
Marklin CAN	Motorola
TraintasticDIY	-	Individual addressing and independent control of state.
XpressNet	-
Z21	-

[reinder]

@gfgit @memen45 what do you think?

[gfgit]

By Single output you mean something like a LED light or a realis, using only one electrical wire from decoder?
And 'Pair' is 2 wires for the 2 states of turnout?

I struggle to think like that, mainly because I don't have a turnout decoder so no way to test but if it works for you than ok

[reinder]

By Single I mean a single output that can be controlled individually. The Z21 (and ECoS) protocol don't support that. LocoNet can technically support it but a command station (e.g. the DR5000) does auto disable it after N ms. The DCC-EX output command is a true single output.

[reinder]

Extended first post with table for investigating output control behavior in different systems, see also #56 (comment)

[reinder]

For signal control using aspects e.g. DCCext is also an option, did some tests with it lately.

That made me think, the OutputController should be refactored, it should support different types of outputs:

• Single digital outputs
• Pair outputs (common for accessory decoders)
• Aspect outputs, e.g. DCCext

Each output channel will have a single output type.
Currently a channel has a custom name, but changing this to an enum (there are not many different channels) makes it easier to tweak the UI for a better UX, see #21.

[reinder]

Implemented in #95