Refactoring of nextcloud code

[fel115]

#75 (comment)

Refactor the Nextcloud Commands loop.

[horenso]

I'm working on the config of the PIN in the nextcloud loop. Do we refactor the config to have the mutex in the config?
I want to set the PIN code via Nextcloud, I could do the same as in Signals where Nextcloud takes a Arc<Mutex<Config<'a>>>
and then we refactor the Mutex in Config afterwards, or should we do this before? @fel115

[fel115]

I think it would be better to refactor the config before as we have problems with the execution of config.sync() in the signals module. We always get a panic, by executing the sync function in the signals module.

Maybe we could also use a get_background_task for config. So we don't need to use mutex and remember/restore baseline (env), set alarm and set pin can be handled by this function. By this method we only need to get the environment data to the config file to restore baseline.

[markus2330]

Changing of PIN is only one of many commands and not the most important one, so please implement the other commands properly first (refactor the code that implements the commands).

I updated the full list of commands in the use case #125. But the system should be flexible and new commands should be easy to add.