refactor: replace node-fetch with axios and fix http proxy

[lvzhenbo]

1. While troubleshooting the download timeout issue, I discovered the following problems:
2. The node-fetch dependency has not been updated for a long time, and its upstream dependency node-domexception has been abandoned.
3. The download proxy settings were not actually taking effect.
4. So I replaced node-fetch with axios, which supports proxies.

[1111mp]

Starting with version 21, Node.js has consistently supported the native fetch API, so I feel that switching to the native fetch would be better.

[lvzhenbo]

But native fetch doesn't seem to support proxies
To be precise, proxy support is not yet available.

[1111mp]

This can be achieved through here.

import { ProxyAgent, setGlobalDispatcher } from "undici";

// ...

const httpProxy =
    process.env.HTTP_PROXY ||
    process.env.http_proxy ||
    process.env.HTTPS_PROXY ||
    process.env.https_proxy;

if (httpProxy) {
  const dispatcher = new ProxyAgent(httpProxy);
  setGlobalDispatcher(dispatcher);
}

// ...

[1111mp]

Starting from Node.js v24, fetch() can automatically use proxy settings without additional code or ProxyAgent. Enable this feature by setting:

export NODE_USE_ENV_PROXY=1
export HTTP_PROXY="http://proxy.example.com:8080"
export HTTPS_PROXY="http://proxy.example.com:8080"
export NO_PROXY="localhost,127.0.0.1,.internal.example.com"

With NODE_USE_ENV_PROXY=1, fetch() respects HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables.
For details, see the implementation PR: nodejs/node#57165

[lvzhenbo]

If you want to use native fetch, then I will close this PR

[1111mp]

I think we can keep the PR open.

This can be achieved through here.

import { ProxyAgent, setGlobalDispatcher } from "undici";

// ...

const httpProxy =
    process.env.HTTP_PROXY ||
    process.env.http_proxy ||
    process.env.HTTPS_PROXY ||
    process.env.https_proxy;

if (httpProxy) {
  const dispatcher = new ProxyAgent(httpProxy);
  setGlobalDispatcher(dispatcher);
}

// ...

Currently, I prefer this option.

However, it seems reasonable to upgrade the Node.js version used by the project since its inception to v24 (currently v20).

[1111mp]

If you want to use native fetch, then I will close this PR

I still believe this PR is fully relevant, so there is no need to close it. The next step is to finalize the solution and proceed with implementation.

[lvzhenbo]

Alright, I'm leaning toward a mature, ready-to-use solution since I did run into issues downloading the binary files. Feel free to reach out if you need further assistance.

[1111mp]

@lvzhenbo If you have time, could you check whether the latest code works as expected. Is the agent working as expected?

[lvzhenbo]

The proxy for undici can be used.