Decide on consistent naming for BIP 32 (hierachical deterministic wallets) concepts

[nicole-obrien]

I think we need to discuss and decide on a consistent naming conventions for BIP 32 (hierachical deterministic wallets) concepts.

Taken from my comment on discord:

Currently the application (firefly) itself can be referred to as a wallet; then you have profiles which have a 1-1 mapping to a seed (again people see these as individual wallets); then within a profile you can make wallets (which I think people see as sub-wallets, technically called accounts in BIP32 - Hierachical deterministic wallets); and in some languages profile and accounts can be synonymous.
As you can tell, it can be a little confusing.

I think we need to decide on the technical terms used internally within the code, and if different we also need to decide on the logical user facing terms used within the UI. Ideally these should be the same, but the technical terms might not be user friendly, and vice versa. I think it's important to value the technically correct in the code and user friendly on the UI; if they are not the same we need to ensure there is no overlap with different meanings. i.e. if the level 2 is called account in the code we cant use the same term for any other levels on the UI.

I will comment my initial proposal soon.