fix(js/core): allow Gemini propertyOrdering in schema validation

[a2105z]

Summary

• Register Gemini's non-standard propertyOrdering JSON Schema keyword with Ajv so structured-output schemas that include it no longer fail with strict mode: unknown keyword.
• Add unit coverage for compile and interpret validation modes, including a case that still rejects invalid data when propertyOrdering is present.

Fixes #3764

Test plan

• npm test in js/core (179 tests passing)
• Reproduce the original ai.generate + output.jsonSchema.propertyOrdering case and confirm it no longer throws

[gemini-code-assist]

Code Review

This pull request registers the non-standard propertyOrdering keyword in Ajv to prevent strict mode validation errors when processing Gemini structured output schemas. It also adds corresponding unit tests to verify that schemas containing propertyOrdering are correctly validated in both standard and interpret modes. I have no feedback to provide.

[a2105z]

Hi @pavelgj @ssbushi — whenever you have a moment, could you take a look at this small js/core schema fix and approve the pending fork workflows if needed?

It registers Gemini's non-standard propertyOrdering keyword with Ajv so structured-output schemas no longer fail strict validation (Fixes #3764). Thanks!