Inconsistency between OSC and OSI for custom traffic actions

[caspar-ai]

Describe the bug

Both OSC 1.0 and OSI provide definitions for custom actions to be specified. These allow for a user to configure custom strings in a scenario which are then passed via OSI at runtime to the system under test.

In OSC it is possible to specify two string values (type and content) and in OSI only one (command).

Describe how to reproduce the bug

OSC documentation: https://releases.asam.net/OpenSCENARIO/1.0.0/Model-Documentation/content/CustomCommandAction.html

OSI definition: https://github.com/OpenSimulationInterface/open-simulation-interface/blob/master/osi_trafficcommand.proto#L484

For clarity, in OSC you might see XML values like:

• <CustomCommandAction type="manoeuvre">ExitHighway</CustomCommandAction>
• <CustomCommandAction type="sensor-failure">FrontRightCamera</CustomCommandAction>

Describe the expected behavior

They should be consistent.