fix(ajv): preserve escaped field names in validation errors

[Marve10s]

Proposed Changes

AJV resolver errors for fields containing / or ~ are returned under encoded or incorrectly nested names. React Hook Form cannot associate those errors with the registered field or its ref.

Decode each JSON Pointer token before constructing the RHF path. Keep a required property's already-decoded name as a single segment so it is neither split at / nor decoded twice.

Reproduction on 5.9.1:

import { ajvResolver } from '@hookform/resolvers/ajv';

const schema = {
  type: 'object',
  properties: { 'a/b': { type: 'string' } },
  required: ['a/b'],
};
const { errors } = await ajvResolver(schema)(
  { 'a/b': 1 },
  undefined,
  { fields: {}, shouldUseNativeValidation: false },
);
console.log(Object.keys(errors));

Before: ['a~1b']. After: ['a/b']. A missing required a/b also stays under that field instead of becoming errors.a.b.

A frozen install currently fails on unchanged master because package.json requires ATA validator ^1.23.0 while bun.lock records ^1.2.0. The manifest and lockfile are unchanged by this PR.

[github-actions]

🎉 This PR is included in version 5.9.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀