feat: keep comment-hack keys above preceding key

[forivall]

Fixes #1

the appropriate formatting of comments should be to put most of your comment in the key itself, like:

  "// Check with maintainer before adding anything!!": null,
  "dependencies": {
    ...

This is still a work in progress to add the functionality for nested things (like the scripts field), but it passes the test I added, so 🎉

[fisker]

This seems too complicated to me.

['//z', '//x', 'z', ' //name', 'name', 'a', '// end']
 -> keys without `//`: ['z', 'x', 'name', 'a', 'end']
 -> sort: ['a', 'end', 'name', 'x', 'z']
 -> restore: ['a', `// end`, '//name', name, '//x',''x', '//z', 'z' ]

WDYT?

[forivall]

if anyone can think of simpler ways to do this, i'm all ears.