fix(maestro): stabilize wallet import and token detection tests

[EdgeClaws]

Summary

• Stabilize C000035 after raw-key export by waiting for the Raw Keys overlay to disappear.
• Give the create-wallet search input a real createWalletSearch testID.
• Skip the clear-button tap before the first empty wallet search and use the named clear-button ID between later searches.
• Stabilize C000034 by falling back to the wallet's Add / Edit Tokens route when the transient Tokens Detected notification does not open Manage Tokens.

Failures reproduced

• C000035 unchanged on Pixel 6: 0/5 passed. In all five runs, Maestro reported the Raw Keys close tap as successful while the overlay remained. Obscured controls behind it then falsely matched; undefined.clearIcon was only the first genuinely absent selector.
• C000034 unchanged on Motorola moto g power (2022): 8/9 valid runs passed. The real failure remained on SHIB asset detail after the transient Tokens Detected notification route was missed. A tenth attempt ended in DeviceServerDiedException and was excluded.

Verification

• C000035: two consecutive full Pixel 6 passes on local Android build 147697b96 (6m45s and 6m48s).
• Android APK build passed for the C000035 app-code change.
• Maestro syntax passed for C000034 and C000035.
• Pre-commit validation passed: TypeScript and 99/99 Jest suites, 731/731 tests, 107/107 snapshots.

Remaining verification

• The changed C000034 flow still needs its final consecutive Android rerun. The Motorola is currently claimed by another QA lane, and the Pixel's normal app slot launches black before the Welcome screen even after reinstalling the frozen APK. Those harness failures occurred before C000034 began and are not counted as product/test results.

Scope

• C000034 detect/disable tokens
• C000035 get raw keys
• Shared maestro/common/import-wallets.yaml callers that use multiple asset searches

Worked on by

• EdgeClaws