fixes #4464

the following have been implemented in trezorlib:

• new exception UnexpectedMessageError to raise when Trezor sends a, well, unexpected message
• client.call(msg, expect=SomeType) will raise UnexpectedMessageError whenever expect is not met, analogous to context.call() in core
• all of trezorlib now uses this mechanism to enforce expected responses
• this is type-safe and fully deprecates the @expect decorator, so that has been deprecated & all usages removed from trezorlib
• functions (mostly) in trezorlib.device, which were returning the string from Success(message="...") have been changed to return str | None, and emit a deprecation warning when someone so much as peeks at the resulting str. We'll change them to -> None in v0.14 or maybe v0.15.
• function trezorlib.device.recover was returning a Success instance!! 🙄 got the same treatment, still returns an object that kind of looks like a Success but emits deprecation warnings if you touch it.
• trezorlib CLI calls using these functions were modified so that they don't print the return value anymore. That's the Unix convention: on success, don't print anything.
• a couple protobuf fields coming from Trezor to device were changed to required
• changed device.reset to a deprecated kind-of-like-an-alias to newly introduced device.setup.
• there is no more separation between reset and reset_entropy_check: the entropy check is an integral part of device.setup, and by default the function will pick a random number of entropy check rounds
• device.setup accepts a private argument _get_entropy() which makes it easier to supply external entropy when needed (such as in tests)
• tests were updated to deal with these changes
• added testcases that check expected_responses for the entropy check flow