Reconsider `fcli state` structure

[rsenden]

It seems a bit overkill to have a top-level fcli state module with only a single variable sub-entity. Variable-related functionality would also fit perfectly well in the util module.

So, to keep the fcli command tree more concise, proposal is to move the state commands as follows:

• fcli state clear -> fcli util state clear: Clears all transient state, like variable data, session data, ...
• fcli state variable * -> fcli util variable *

The only potential drawback is that if we ever want to have additional state-related commands (although I can't think of any right now), these would likely also need to go into the util module, or we might need to revert to having a dedicated state module.

Ideas/suggestions/...?

[psmf22]

agree with moving it to util, a separate module for 2 commands seems overblown

[rsenden]

Others also seem to agree that moving to util would be better; shouldn't be too much effort so will implement this.