Switch quickly network can corrupt the application configuration

[ValentinTrinque]

When switching network to fast by spamming the button, the “DefaultNetwork” get overwritten so fast that the file is left with previous character, corrupting the file.

We should prevent the user to trigger that update to fast.

Notice the extra e at the end, probably from the false value of a previous config.

[radoslaw-szpiech]

Also, there is connected issue with that If you you switch path to config catalog, that does not exist, you get screen as below: At this point:

• User should be informed, that there is no such catalog, or .toml files do not exist.
• There should be some "back" button.
• User is blocked at this point. Even if the app is closed and reopened, only this screen is visible. It should not save config catalog without confirming it's existing and contain correct .toml files.

EDIT: Also, the path on this screen is not the one that I used.

[radoslaw-szpiech]

UPDATE: It looks like it cannot be reproduced just by switching to not existing catalog, as it just creates new catalog then. It was fixed during writing my comment, or I was just unlucky to experience that. There is still valid issue, if we use Path, that cannot be simply accessed by User - https://github.com/vegaprotocol/vegawallet-desktop/issues/504

[ValentinTrinque]

This is done.