[Bug] Stall flag is always raised for position-based drive commands.

[laurensvalk]

Describe the bug
The stall flag is always raised when doing position-based Drive Base commands.

While we almost never use the stall flag for this use case, it still shouldn't be set.

To reproduce

from pybricks.pupdevices import Motor
from pybricks.parameters import Port, Direction
from pybricks.robotics import DriveBase
from pybricks.tools import wait

left_motor = Motor(Port.A, Direction.COUNTERCLOCKWISE)
right_motor = Motor(Port.B)
drive_base = DriveBase(left_motor, right_motor, wheel_diameter=56, axle_track=112)

# Drive forward without blocking.
drive_base.straight(500, wait=False)

# Wait until done.
while not drive_base.distance_control.done() or not drive_base.heading_control.done():
    wait(10)
    # Check for stall.
    if drive_base.distance_control.stalled() or drive_base.heading_control.stalled():
        # Shouldn't get here but we do!
        break

drive_base.stop()

Expected behavior
Drive without raising the stall flag.

[laurensvalk]

When we fix this, we should add the following flags to the data logger to see this sort of thing more quickly:

• Stalled
• Done/busy
• duty/coast mode active

[laurensvalk]

we should add the following flags to the data logger

Done via pybricks/pybricks-micropython@4f5a0ee and pybricks/pybricks-micropython@662c002