fix(core): ignore unexpected messages in backup flow during setup

[romanz]

Similar to #6483 (backup should not fail due to unexpected messages from host), but for ResetDevice-based backup, which is being used in trezor/trezor-suite#25084.

Related to #6348.

CC: @STew790

This PR doesn't solve I/O error handling (i.e. ButtonRequest write errors due to dead host) -> should be done in #6651.

TODOs:

• improve cancellation test coverage

Note to QA:

Please test on both v1 & THP (e.g. TS5 & TS7):

• run trezorctl device setup -b single (single-share SLIP-39 wallet).
• exit trezorctl with Ctrl+C when the first mnemonic words are shown.
• it should fail with:

Please confirm action on your Trezor device.
^CFailed to end session: InProgress: Backup in progress

Aborted!

• try to run trezorctl ping 123
  • the backup flow MUST NOT be interrupted.
  • trezorctl should fail with:

Failed to connect: UnexpectedMessageError (Expected Features but Trezor sent <Failure: {'code': <FailureType.InProgress: 19>, 'message': 'Backup in progress'}>)

• complete the backup and the quiz - the flow should succeed even with disconnected host.
  • it is expected to show "Your Trezor is having trouble communicating with your connected device." warning after the backup succeeds.
  • it can be dismissed by calling trezorctl ping 123
  • the device should be correctly initialized.

[github-actions]

en main(all)

model	device_test	click_test	persistence_test
T2T1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)	test(all) main(all)

Translations

cs main(all)

model	device_test	click_test
T2T1	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)

de main(all)

model	device_test	click_test
T2T1	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)

es main(all)

model	device_test	click_test
T2T1	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)

fr main(all)

model	device_test	click_test
T2T1	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)

pt main(all)

model	device_test	click_test
T2T1	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)

Latest CI run: 24092783972

[romanz]

Rebasing to resolve a conflict.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@tests/device_tests/reset_recovery/test_reset_bip39_t2.py`:
- Around line 38-41: The FLOW_ADAPTERS entry using try_to_cancel currently skips
{"backup_device", "setup_device", "success_backup"} but misses the
Delizia-specific ButtonRequest name "confirm_setup_device", causing a Cancel to
be injected during setup; update the try_to_cancel call in FLOW_ADAPTERS to
include "confirm_setup_device" in the skipped set (alongside "backup_device",
"setup_device", and "success_backup") so cancellations are ignored for that
setup request as intended.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 97bee016-947c-4897-80e4-47730471e0c8

📥 Commits

Reviewing files that changed from the base of the PR and between 111854f and a331f07.

📒 Files selected for processing (7)

• core/src/apps/management/reset_device/__init__.py
• tests/device_tests/reset_recovery/test_reset_bip39_t2.py
• tests/device_tests/reset_recovery/test_reset_slip39_advanced.py
• tests/device_tests/reset_recovery/test_reset_slip39_basic.py
• tests/device_tests/test_msg_backup_device.py
• tests/input_flows.py
• tests/ui_tests/fixtures.json

🚧 Files skipped from review as they are similar to previous changes (3)

• core/src/apps/management/reset_device/init.py
• tests/device_tests/reset_recovery/test_reset_slip39_advanced.py
• tests/device_tests/reset_recovery/test_reset_slip39_basic.py

[romanz]

Squashed.

[mmilata]

LGTM, nice tests

[mmilata]

Missing return type?

[romanz]

Thanks - fixed and rebased:

1:  9d5556ffa5 ! 1:  dc41f5f3fc chore(core): move backup flow adapters to `tests.input_flows`
    @@ tests/input_flows.py: class InputFlowCancelBrightness(InputFlowBase):
     +    return flow()
     +
     +
    -+def try_to_cancel(skip_cancel: set[str] | None = None):
    ++def try_to_cancel(skip_cancel: set[str] | None = None) -> FlowAdapter:
     +    BACKUP_IN_PROGRESS = messages.Failure(
     +        code=messages.FailureType.InProgress,
     +        message="Backup in progress",
2:  f56509c58b = 2:  77db2ff1b3 fix(core): ignore unexpected messages in backup flow during setup
3:  c86a55a1f9 = 3:  5a94a97682 test(core): test backup cancellation during `ResetDevice`
4:  2d119266fa = 4:  ed22f86ce7 chore(core): update UI fixtures