Put password health results into some kind of global state to cache it per "application session"

[jonas-pietzsch]

The password health should only be reviewed once per application usage.

[jonas-pietzsch]

Refactored the global password-health feature in a way that rating was removed from the rendering process. It is now deterministic when the state is ready and when it has stored a finished password-rating result. This result can be taken to be persisted for a temporary time now. It could be invalidated by:

• Simply time: it gets a max age, when it's over the check will run again
• All secrets' checksum (can we get a checksum over all stores from Gopass?!): if something changed, calculate again
• Edited/removed/added secrets through Gopass UI. Disadvantage of not tracking modifications via CLI...

[jonas-pietzsch]

TODO: put the finished results into the system settings. First iteration will use the "simply time" implementation to keep it simple ATM.

[svenXY]

In addition, it would be great if one could go back to the list directly after having selected and inspected one of the suggested improvements.

Besides, except the colour, it is not clear that these passwords can be clicked on in the first place. At least the cursor icon could change or similar