Switch from JSON to KDL format

[Bashamega]

#2053

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @saschanaz - if they write a comment saying "LGTM" then it will be merged.

[saschanaz]

Err, I was saying that I'd like to add a new topic-separated files in KDL, not converting existing monolithic file to KDL.

[jakebailey]

Is this formatting a mistake? This is pretty unreadable, way worse than described in the linked issue with the braces and so on

[Bashamega]

I understand @saschanaz
I am just converting the data for now, and trying to see if it works, when It works I will split them into sub files

[saschanaz]

Sounds good, but let's do it one by one in each PR so that the PR can be reviewed and merged separately!

[saschanaz]

(I think we don't need to keep quirks like methods.method in KDL, we can skip that in KDL and convert to the existing JSON format (we'll need such conversion as KDL parse result itself will never be compatible as-is.)

[Bashamega]

Hello @saschanaz
Currently, I am working on the read function.
And I found an issue with KDL that I can't find a fix for.
Some arrays only have one item, so KDL doesn't treat it as an array.
How can I make it an array?
I can only come up with one solution, which is when I want an array with one item and another item called, for example, KDLARRAY, and we will drop it when converting.
If you have a better solution, please tell me