Notify user that CLI and Desktop settings and data files are independent

[darkk]

OONI CLI and OONI Desktop applications have different home directories, different "upload spools" and different settings.

But that may be unexpected UX for Linux users. E.g. vim and gvim use same .vimrc file. Maybe there are other applications having same pattern for GUI and CLI versions of the app.

I suggest to add some code to probe-cli and probe-desktop that notifies user about that difference during, for example, onboarding process in the app.

E.g. if ooni-desktop sees a per-user or "global" ooni-cli home directory li during onboarding, it should notify the user that ooni-desktop DOES NOT use ooni-cli home. So user should not expect ooni-desktop to manage ooni-cli spool.

/cc @ooni/design

[hellais]

I do actually wonder if this is indeed the desired behaviour or if we want to allow the ability to control the GUI data dir via the CLI and vice-versa.

I figured that keeping them separated would be been less surprising to a user, but maybe that is not the case.

We should consider these two options.

[bassosimone]

My understanding is that vim and gvim come from the same codebase. This is not the case because we'll have two implementations. I agree that it's tricky. (OTOH Linux users are expected to mainly use the cli, so maybe MacOS users are the ones that are going to be surprised.)

[hellais]

This is no longer relevant in light of: #2845