[BUG FIX]: Axios to Fetch Migration

[proffapt]

What?

Migrated to use Fetch for making network calls instead of Axios. This is the fix which allows the creation of Metamask Snaps.

Why?

https://docs.metamask.io/snaps/how-to/troubleshoot/#axios

As mentioned clearly in the above section of official documentation of Metamask Snaps, they run in a sandboxed environment in which axios doesn't work, always leading to this very error. In addition, none of the solution provided in that issue thread works in this case either.

Test Plan

Can be tested on a template snap

[trunk-io]

⏱️ 14s total CI duration on this PR

Job	Cumulative Duration	Recent Runs
permission-check	4s	🟥
permission-check	4s	🟥
permission-check	4s	🟥
permission-check	2s	🟥

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[0xmaayan]

@proffapt Thank you for the PR.

The Aptos SDK provides a custom client configuration where one can override the existing client (i.e axios), can check out this example where we use fetch as a custom client https://github.com/aptos-labs/aptos-ts-sdk/blob/main/examples/typescript/custom_client.ts#L21

Additionally, this change requires comprehensive testing of the SDK, and we should explore the tradeoff between axios and fetch more.

[proffapt]

Hi @0xmaayan ,

I didn't know that aptos provides custom client configurations. The reason for making this PR is mentioned in the PR message. This custom client should solve my problem now (for which I wrote this migration from axios to fetch).

I am closing the PR now.