fix: normalize response bytes in getKeysFromRelayer

[luchobonatti]

Closes: zama-ai#378

Summary

• Replace inline response.bytes() / response.arrayBuffer() logic in getKeysFromRelayer with the existing getResponseBytes() utility
• getResponseBytes() already uses normalizeBytes() which handles Uint8Array, ArrayBuffer, and ArrayBufferView — fixing the case where undici (Next.js) returns ArrayBuffer from response.bytes()

Changes

File	Change
src/relayer-provider/v1/networkV1.ts	Replace 2 inline byte-reading blocks (12 lines) with getResponseBytes() calls (2 lines)

Test plan

• prettier:check passes
• eslint passes
• networkV1.test.ts — 1 suite, all pass
• fetch.test.ts — 1 suite, all pass

[Copilot]

Pull request overview

This PR normalizes relayer key/CRS response body handling in getKeysFromRelayer by reusing the shared getResponseBytes() utility, improving compatibility with fetch implementations (e.g., undici/Next.js returning ArrayBuffer from response.bytes()).

Changes:

• Replace inline response.bytes() / response.arrayBuffer() branching with getResponseBytes() for the public key fetch.
• Replace inline response.bytes() / response.arrayBuffer() branching with getResponseBytes() for the CRS (2048) fetch.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

getResponseBytes() already returns a Uint8Array, but later this buffer is wrapped with new Uint8Array(publicParams2048) before deserialization. That constructor call will clone the entire CRS byte array, which can be very large and adds avoidable memory/CPU overhead. Since the bytes are already normalized, pass publicParams2048 directly to CompactPkeCrs.safe_deserialize(...) (and drop the extra new Uint8Array(...)).