Multiplexed DBC message implementation has some (poor) assumptions

[amund7]

Assumptions:

• Only 1 mux per CAN ID
• multiplexer indexer comes before the (and must be decoded before!) other values

These assumptions will probably fail at some point.

Maybe the sub-messages can be sorted during load, to make sure the indexer is always decoded and stored before the others?