[Feature] Raise runtime errors for likely misconfigured builds

[laurensvalk]

Is your feature request related to a problem? Please describe.
Quite often, we get reports about things not working, when it is an issue of plugging motors in the wrong port or with the wrong direction.

In particular, we get these two quite often:

• When the left and right motor are swapped or reversed by mistake, a drivebase appears to work normally when using the rotation sensors, but it will run in circles indefinitely in gyro mode because this creates a positive feedback loop.
• When people try the car code before they build the car, the steering motor will turn forever because there aren't any end stops. This will give apparent issues like "the remote doesn't connect" when this isn't the cause.

Describe the solution you'd like
When a steering motor spins unreasonably far, raise a RuntimeError saying something like "No steering mechanism on Port A."

When a gyro drivebase spins out of control, say something like "Check the left and right motor configuration".

[laurensvalk]

The runtime error for the car can conveniently be done in the class setup.

For the gyro drivebase, the issue will only occur when starting to move. I'd rather not risk raising unexpected runtime errors, so maybe we shouldn't try to capture this for the drivebase.