Feat/chunk logging

[devceline]

Changes

• Add 2 new logger classes:
  • ServerChunkLogger: Extends Writable from stream and can be injected into pino. Built for Node.js
  • BrowserChunkLogger: Simple wrapper around a write function to be injected into pino. Built for Browsers and React Native.
• Both use a CircularArray to maintain logs. Went with this because logging is such a frequent operation so we'll need frequent appends and deletions.
• Both maintain a max size in bytes
• Added helper functions to make this clearer for when we add these to core
• Have "Console Forwarding" in both:
  • Within the chunk logger, all levels are stored. ( pino level == "trace" ). However, if a log matches the dev specified level (eg: "warn") or above (eg: "error") it gets forwarded to the console.
• Add Tests for this

Motivation

https://walletconnect.slack.com/archives/C03RME3BS9L/p1710438640477839

[devceline]

Went back to original implementation of linked list because of the following edge case:

This was the scenario I was trying to talk about in my comment. It's deleting entires even though there is capacity remaining Max capacity 16 bytes Insert aaaa, bbbb, cccc, dddd [aaaa, bbbb, cccc, dddd] - at capacity Insert e [e, bbbb, cccc, dddd] - 3 capacity remaining Insert f [e, f, cccc, dddd] - 6 capacity remaining An alternative (I think how it works now) is to add to the end. But the issue here is now it's out-of-order: Max capacity 16 bytes Insert aaaa, bbbb, cccc, dddd [aaaa, bbbb, cccc, dddd] - at capacity Insert e [e, bbbb, cccc, dddd] - 3 capacity remaining Insert f [e, bbbb, cccc, dddd, f] - 2 capacity remaining Only solution would be to INSERT, but then we are doing shift operations which are >=O(n) - Chris (from slack)