The config file use should have better explainations and documentation assitance for the enduser

[mikefaille]

The config path related to perkeep fall on 2 principal usability sub-issues :

1. the configuration could be more familiar for endusers. Or, it should be easy to retrieve the actual config path since there is many branch on the logic to generate the full path of the configuration file to retrieve : server/perkeepd: Add hints for newcomers about config source #1387 (comment)
2. Since the directory containing the configs could change according the OS, it's possible remote storage to use and the logic to retrieve the configuration is not documented, it would be important to get a clear documentation without needing any assumption from the enduser knowledge about Perkeep behaviour.

A suggested requirement to solve this issue :

• we should be able to predict where the configuration file path would be with enough documentation and we should be able to choose the right configuration in the first place without try and error as explained here server/perkeepd: Add hints on -help for newcomers about config dir #1388 (comment)