[Bug] LWP3Device.read is blocking

[laurensvalk]

Describe the bug
LWP3Device.read() was not updated to be async.

For some reason I was thinking that it worked like reading the remote button state cache, so I never implemented async for this one. But it is a blocking call.

Expected behavior
Either not block (read latest) or be async.

Suggestions
If messages get lost anyway (they are overwritten), perhaps it can just be a non-blocking read like the buttons, instead of implementing async. Use case: reading the duplo train color. Just reading the latest value would suffice.

[laurensvalk]

cc @NStrijbosch via https://github.com/orgs/pybricks/discussions/1372

[NStrijbosch]

Some details on the rationale for the read being blocking right now:

pybricks/pybricks-micropython#68 (review)