[Doc] Document positive_direction for DriveBase

[laurensvalk]

Describe the issue
Need to document this new feature: pybricks/pybricks-micropython@6e2f703

[laurensvalk]

While we do that, also document deceleration setting consistent with single motors: pybricks/pybricks-micropython@77f3ebd

[laurensvalk]

Auto-close did not work, so close manually.

[laurensvalk]

Since this isn't released yet, I think it's worth giving this a closer look.

Based on user feedback on gyros, I'm starting to think it could be worth having a separate GyroDriveBase class instead of adding the use_gyro option to the DriveBase.

• This makes it a more obvious separation between two rather different behaviors.
• Users could switch between the two to see these differences, instead of messing with setup arguments.
• We can also transparently take care of the positive_direction this way.
• This whole class can be disabled on platforms without a gyro, instead of raising exceptions for certain combinations of arguments
• And, well, the pybricks.robotics module is a bit empty after all.

Internally, all of the code is still shared, so this is not a increase in code size. On Move Hub, it should even go down a bit since we'd omit the positive_direction and use_gyro arguments this way.

[laurensvalk]

And separately from this, maybe heading() does need to be positive clockwise, as well. This seems to be more common than I though in navigation systems, including compasses.

There will still be the rotation() method to get the rotations around each axis matching the right-hand rule common in engineering (counterclockwise-is-positive)`.

[laurensvalk]

And separately from this, maybe heading() does need to be positive clockwise, as well. This seems to be more common than I though in navigation systems, including compasses.

Ran a poll:

[laurensvalk]

Based on user feedback on gyros, I'm starting to think it could be worth having a separate GyroDriveBase class instead of adding the use_gyro option to the DriveBase.

Done, so closing.