Physical entries to OverrideControllerValueAction
Describe the feature
The OverrideControllerValueAction has two small issues, that can cause problems. The steeringwheelaction where the input is angle, and the brake where the input is procent.
For both of these, more physical inputs might be desiered for different cases (like the driver is turning while an AD function is turning, then angle makes no sense). For Steeringwheel this would be Torque, and for brake this would be Force.
Describe the solution you would like
There should be a choice in the OverrideSteeringWheelAction, that either you have angle input or torque input. There should be a choice in the OverrideBrakeAction, that either you have procent input or force input.
Describe alternatives you have considered
Only one we thought of is to have a parameter that says "interpret steeringwheelangle as torque" which is a very bad solution
Describe the backwards compatibility
Might be a new entry in the action itself, or a new Action under the OverrideControllerAction, depending on the solution.