Teach convertAjvErrors to provide an even better UX

[nulltoken]

This is a follow up to #1530

• Some paths were still not properly dealt with. This change proposal helps them render as expected. Unit tests have been added to cover those use cases.
• When the schema requires some properties, and they've found missing in the passed in object, the error message states the name of the offending property (eg. ``). However, when the schema forbids any additional property to be added to an object, the error message is a bit unhelpful (ie. should NOT have additional properties). This change proposal adds the name of the superfluous property in the error message (eg. `should NOT have additional properties; found 'neither'`)

[nulltoken]

@XVincentX I'm not quite sure where did the initial slice(1) come from. Nor what requirement it was fulfilling.
Switching to a split('.') call seems to still not break any test while making the code a bit easier to reason with.

[kikisaeba]

Hi,
I'm interested by this change.
When could it be merged ?

[XVincentX]

Hi,

I'm interested by this change.

When could it be merged ?

We try to look at PRs in a timely manner and try to release as long as we have meaningful changes.

TL;DR: no ETA.

[nulltoken]

@XVincentX 👋 Any chance you could take a look at this?

[XVincentX]

I'll try to get on this asap; I need to do a sanity check as well as reviewing the code.

I want to make sure we're not bloating the function with edge cases and see if there are some split opportunities.

I'll keep you posted.