Config validation; duplicate key wrong error

[Bad3r]

Error in Logseq:

Failed to read file 'Pandora/logseq/config.edn'. Make sure your config is wrapped
in {}. Also make sure that the characters '( { [' have their corresponding closing character ') } ]'.

I triggered this error while testing what happens when you have a duplicate key.

Steps to reproduce:

1. open config.edn and duplicate any config key/value
2. Logseq displays unrelated error

side-note

in the previous version; when a config is duplicate; Logseq used to consider the config file broken.
I think the way duplicate config should be handled is that;
the last occurrence gets to set the value for the key.

i.e. if the config file contained:

 :ref/default-open-blocks-level 2
 :ref/default-open-blocks-level 3

the value of :ref/default-open-blocks-level would be 3.
Logseq can display a warning, but it should continue to
work as expected.

[logseq-cldwalker]

Agree it could be nice to have a more specific error message for this case. Looks like the error message thrown makes this doable. Leaving this open as a good first issue for whomever

For whomever takes this on, please use notfication/show! to display the error and the error to be caught is in validate-config-edn