fix: escape schema values in generated code

[mcollina]

Summary

• stop embedding schema references directly into generated comments, template literals, validator calls, and regular-expression literals
• encode complete generated error literals, including required-property errors
• escape JSON Pointer tokens and URI-fragment characters in generated validator references
• reject active schema identifiers containing block-comment terminators when Ajv source generation is enabled
• add regression coverage across normal, debug/restore, standalone, and inline-validator modes

Rationale

The README requires schema definitions to be trusted application code. This change preserves that trust model while ensuring schema-derived strings cannot accidentally change generated JavaScript or resolve to the wrong validator path.

Validation

• npm test — 514 tests passed; 100% statement, branch, function, and line coverage
• npm run lint
• targeted tests on Node.js 20, 22, 24, and 26
• npm pack --dry-run
• git diff --check

[gurgunday]

lgtm

[Tony133]

LGTM, two small things (not blocking):

• the description still talks about escaping comments and validator refs, but that part is already on main (asComment, JSON.stringify(schemaRef) in buildOneOf/buildIfThenElse) — might want to trim it so the changelog matches what's actually in the diff
• percent-encoding the JSON pointer changes error messages, e.g. first name becomes #/properties/first%20name. Correct per RFC 6901 and Ajv decodes it fine, but let's mention it in the release notes