add line/column number to syntax errors

[mark-pictor-csec]

I can use other tools to track down an error, but it'd be nice if jd could provide the location itself.

compare jd's behavior with a bad file with that of jq:

$ jd defsck_p.json defsck_f.json           
2024/02/23 15:32:17 invalid character '(' in string escape code

$ jq <defsck_p.json 
parse error: Invalid escape at line 49883, column 1295

[josephburnett]

This is a limitation of Golang's bulitin JSON parser. Maybe there is a better one that can give that kind of specific error. Would be really nice for sure!

[josephburnett]

@mark-pictor-csec If I were to implement this issue: #83 to parse with the YAML library and keep YAML types internally, then you should get much better errors. https://pkg.go.dev/gopkg.in/yaml.v3 has really good syntax errors so it will point on where you went wrong.