Gold 111: update to use unified fast stable stringify

[arhamj]

No description provided.

[linear]

GOLD-111 Migrate explorer repo to use unified stringifier and custom revived parser

ISSUE SUMMARY:

<<TODO: Replace this with a short summary of the issue.>>

---

ISSUE REPRO STEPS:

<HINT: Add steps to list as-needed. If interaction is complex, add screenshots or a Slack screen-capture video (just drag and drop)>

1. <<TODO: Replace with repro step Bump the npm_and_yarn group across 1 directory with 8 updates #1>>
2. <<TODO: Replace with repro step Bump the npm_and_yarn group across 1 directory with 9 updates #2>>
3. Observe <<TODO: Describe unintended behavior.>>

---

EXPECTED RESULT:

<<TODO: Replace this with your expected results.>>

---

PULL REQUESTS:

<HINT: If your fix requires changes in multiple repos, add the following info per-repository.>

<<TODO: Enter Repository Name>>

Pull Request Link: <<TODO: Insert PR-LINK>>

GPT Review Link: <<TODO: Insert GPT-Review-Link>>

Jenkins Test Link: <<TODO: Insert Jenkins Test Job Link>>

---

ADDITIONAL INSTRUCTIONS:

<HINT: Add any additional instructions needed for the assignee. If you have specific requirements for how the task should be implemented or fixed, enter them or link them here.>

<<TODO: Insert additional instructions for assignee.>>

[S0naliThakur]

LGTM

[abdulazeem-tk4vr]

Summary of changes :

• Porting over to safeStringify and safeParse in the backend
• Using the typeReviver in the client side of the explorer for appropriate parsing using axios interceptors.

The changes look good to me. We can ship this to production.