improve error reporting JSON vs YAML

[neolit123]

the errors of this library need work.
with the strict JSON decoder unknown fields would result in errors such as:

error unmarshaling JSON: .....: json: unknown field "z";

this gives a hint that "z" is unknown.
but the user would first of all be confused why is the error throw to stdout about JSON, while their e.g. manifest is in YAML.

xref: #7

[neolit123]

/kind cleanup
/priority important-longterm

[errordeveloper]

It would be great if we could fix this, the error messages are very very confusing to end-users.

[neolit123]

problem here is that all the backends out there including encoding/json yaml.2/3, json-iter don't have good typed errors. this leaves us in a space where we need to parse strings, modify them and return proper errors.

i'm -1 on that, so it's probably best to wait on the backends to fix them, or attempt to push patches upstream.

/remove-kind cleanup
/kind design
/remove-priority important-longterm
/priority backlog

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[neolit123]

as explained here this is far from ideal:
#9 (comment)

if someone wishes to help please open tickets for yaml v2/v3 and json-iter.