Add separate control bindings for translation

There is a mismatch between translation/pitch, roll, yaw input pairings across platforms as follows.

PC
Pitch, translate forward
Roll, translate Up
Yaw, translate Right

Mobile(IOS)
Pitch, translate up
Roll, translate right
Yaw (left stick all axes) translate forward

I think it's too late to change them as it would frustrate a great number of users.
I suggest adding translation fields to the control bindings options. That way the user can decide whether to have the same pairings across platforms or stick with the established default.