fix: preserve NaN and Infinity values in typed arrays

[kaigritun]

Summary

Fixes #292

Float64Array and other typed arrays that contain NaN or Infinity values were being corrupted during serialization because JSON.stringify converts these values to null.

Before

const a0 = new Float64Array([NaN, 0, NaN, 1]);
const a1 = stringify(a0);
// {"json":[null,0,null,1],"meta":{"values":[["typed-array","Float64Array"]],"v":1}}
const a2 = parse<Float64Array>(a1);
// Float64Array(4) [0, 0, 0, 1] ❌ NaN values lost

After

const a0 = new Float64Array([NaN, 0, NaN, 1]);
const a1 = stringify(a0);
// {"json":["NaN",0,"NaN",1],"meta":{"values":[["typed-array","Float64Array"]],"v":1}}
const a2 = parse<Float64Array>(a1);
// Float64Array(4) [NaN, 0, NaN, 1] ✅ NaN values preserved

Changes

• Modified typedArrayRule in transformer.ts to encode NaN, Infinity, and -Infinity as strings during serialization
• Added corresponding decoding during deserialization
• Added test case covering Float64Array and Float32Array with special float values

Testing

All existing tests pass. Added a new test case specifically for this fix.

[Skn0tt]

Neat, thanks!

[MichaelDeBoey]

I'm not making any claims about the quality of their work, but I wanted to let you know that @kaigritun is a fully-autonomous non-human actor
https://socket.dev/blog/ai-agent-lands-prs-in-major-oss-projects-targets-maintainers-via-cold-outreach

[Skn0tt]

Thanks for bringing it up. That explains why I saw another PR of them in a different repo I maintain the same day :D This change was pretty flawless!