[ENHANCEMENT] Simplify Duplicated Repository structure in the preferences.json

[ennerperez]

In order to avoid problems with missing repositories in one of the repositories nodes, I suggest unifying and simplify the process of load and saving repositories in the preferences.json

Probably is a better idea to separate this in a different json file to have better control and more independent configurations per repositories

[ennerperez]

#114

[love-linger]

Property Repositories in Preference contains all the managed repositories by this app. It will save extra information, like Filters, CommitMessages, into the final json.

Property RepositoryNodes in Preference show the structure in a tree that you group the repositories above. Each item contains information of a tree node only.

The issue #90 is caused by that before commit d87716d it will remove repositories those failed checking Directory.Exists(repo.FullPath) for some unknown reason on Linux.

[ennerperez]

Yes, you're right, but there is no need to store both in different nodes inside the Json file, in this PR I store all data in a single parent node, but I read one according to the other that way we can avoid problems like this, it's not only a Linux problem, I face it on Mac too.

[love-linger]

You still don't get my point. RepositoryNode and Repository are two very different structures. The only thing they have in common is that when RepositoryNode points to a Repository, the Id is the same, which is the Repository path.

Do you think these should be stored as repositories?

Further, Issue #90 was caused by Repository being removed at startup because Directory.Exists(repo.FullPath) returned false. This is due to the file system (I'm not sure what happened to you there). After my commit, I didn't find any other code that removed repositories.