fix(scalars): correct jsonSchema definitions that misdescribe their values

[ifeanyi-ugwu]

Several scalars ship a jsonSchema extension that rejects values the scalar serializes or declares the wrong type. This corrects each to match the serialized output.

Rejecting values the scalar accepts:

• SESSN — SESSN_PATTERNS held the format placeholders YYYYMMDDXXXX / YYMMDDXXXX, used verbatim as regex patterns, so they matched only that literal text and no real personnummer. The length beside them is not a JSON Schema keyword. Replaced with real patterns for the two accepted forms under anyOf.
• PostalCode — used oneOf over the per-country patterns, but postal formats overlap (a 5-digit code matches US, DE, FR, IT, ES at once), so a valid code matches several patterns and fails oneOf's exactly-one requirement. Changed to anyOf.
• LocalDateTime — format:'date-time' mandates an RFC 3339 offset, which an offset-less LocalDateTime never has. Uses the scalar's own regex as pattern, like LocalDate and LocalTime.

Mismatched serialized output:

• Timestamp — declared type:'string', but serialize returns a number of milliseconds. Now type:'integer'.
• BigInt / Long — int64 implies a 64-bit bound a BigInt does not have and omits the decimal-string form used beyond the safe-integer range. Now oneOf:[integer, numeric-string].
• USCurrency — the pattern forbade the thousands separators and leading minus that toLocaleString produces, so it rejected the scalar's own output above $999 and for negatives. Widened to match.

[ardatan]

Those format values are actually heavily used in OpenAPI spec. So I am not sure if they should be considered as non-standard.
https://swagger.io/docs/specification/v3_0/data-models/data-types/

[ifeanyi-ugwu]

Those format values are actually heavily used in OpenAPI spec. So I am not sure if they should be considered as non-standard. https://swagger.io/docs/specification/v3_0/data-models/data-types/

byte and int64 are standard OpenAPI formats and "non-standard" was wrong. These annotations feed SOFA, which emits OpenAPI, so OpenAPI's format vocabulary applies.

I dropped the Byte change. serialize returns a Buffer and Buffer encodes on the wire as {"type":"Buffer","data":[...]}. type:'string' mis-describes that output whether the value carries format:'byte' or a pattern. Byte will need its own change.

PostalCode, SESSN, USCurrency, and LocalDateTime reject values the scalar emits.

Timestamp declared type:'string'; serialize returns a number.

BigInt moved to oneOf:[integer, numeric-string]. A BigInt isn't 64-bit-bounded. It serializes as a string once it passes the safe-integer range. int64 captures neither. If SOFA already emits out-of-range int64 as a string, int64 alone suffices and I'll switch back.