Change the EVM legacy discovery error on old firmware

[enjojoy]

Description

Changed the error message for non-normal EVM account types, when discovery error occurs.

Related Issue

Resolve #14638

Screenshots:

[tomasklim]

This means, that if it is normal, there is

[enjojoy]

Right, let me remove the " "

[enjojoy]

Removed, now the space will be only when the type is not normal

[tomasklim]

https://github.com/trezor/trezor-suite/blob/develop/COMMITS.md

[enjojoy]

https://github.com/trezor/trezor-suite/blob/develop/COMMITS.md

sorry, no idea how I could forget this. reworded.

[Hermez-cz]

The copywriting is clear and concise, directly explaining the issue. However, the [Retry] CTA feels out of place. From the user's perspective, a CTA to update the firmware would be more appropriate, as retrying will lead to the same result without the update. Since we can't change the flow at this point, how about adding '(see the blue banner above)' at the end of the body text?

[enjojoy]

The copywriting is clear and concise, directly explaining the issue. However, the [Retry] CTA feels out of place. From the user's perspective, a CTA to update the firmware would be more appropriate, as retrying will lead to the same result without the update. Since we can't change the flow at this point, how about adding '(see the blue banner above)' at the end of the body text?

Sure, I will add this note

[evgenysl]

QA OK

• FW 2.6.0 and newer - no issues with Legacy account discovery

• FW 2.5.3

Message is small and is not present in Legacy account itself (second screenshot), but this is an edge case for firmware from November 2022 and older.