Proposal for more user centric UI/menu structure

I've been playing around a bit with some Specter HW devices and like the open source and feature rich approach.

However, when I compare the menu structure of the firmware with some of the other HW wallets I have (passport, keystone, ...) I find it rather confusing.
Hence I sat down and came up with the following proposal which I hope is more intuitive for most users.

The main idea is to not focus around how the hw works / is structured, but to come from the users perspective asking: what are things users want to do / work flows they might have?

I haven't coded in quite a while, hence it is just a plain text file, but I hope it is intuitively readable.

Also: not all menus/ideas are fully fleshed out / set in stone.

Would be nice if someone could reach out to help get this into real code!

[Specter UI.txt](https://github.com/user-attachments/files/22945349/Specter.UI.txt)

Read the attached Specter UI.txt first; it is the only concrete artifact and the proposal says several ideas are not settled. Then locate the firmware's menu and UI entry points, agree on specific workflows and acceptance criteria, and consider the work done when the agreed structure is implemented and verified.

Written by the indexing model from the issue text.