Release v3.3.0b3

Added

• Added positive_direction to DriveBase initializer. It defaults to
  clockwise to ensure this is not a breaking change. Users can now change it
  to counterclockwise, which is more common in engineering (support#989).
• Added support for setting drivebase acceleration and deceleration separately
  using a tuple, consistent with single motors (support#881).

Fixed

• Fixed allocator interfering with motor control when memory usage is high (support#977).
• Fixed Stop.NONE not working properly for some drivebase geometries (support#972).
• Fixed reading programs larger than 65535 bytes on boot on SPIKE hubs. ([support#996).
• Various Bluetooth stability and reliability improvements on BOOST Move hub
  (support#320, support#324, support#417).
• Fixed Bluetooth random address not changing on City and Technic hubs (support#1011).

Changed

• Methods like control.limits() now check the user input and raise a
  ValueError if a value is out of bounds (support#484). This affects only
  settings setters, which are usually used as a one-off. Nothing changes to
  speed values set at runtime. These are still capped to valid numbers without
  raising exceptions.
• Renamed precision_profile to profile in the Motor initializer.
• In DriveBase, wheel_diameter and axle_track now accept decimal values
  for increased precision (support#830).

Removed

• Removed DriveBase.left and DriveBase.right properties (support#910).