use @napi-rs/canvas instead node-canvas

[hustcc]

Lightweight, we can install it with zero dependence. ref: Brooooooklyn/canvas#1083

[BQXBQX]

After a brief investigation, I think there are three technical solutions

Waiting for @napi-rs/canvas to be updated and fix this issue.

This implementation cost is minimal, but we don't know the exact date of the repair or whether it can be repaired.

Set the Chinese font to the default font of @napi-rs/canvas, sans-serif, and it can be rendered correctly

This implementation has the second lowest cost, but the code will become difficult to understand (why set `SourceHanSans-VF.ttf` as `sans-serif` ?), and the iteration cost may be high in the later stage.

Register Source Han fonts first, then update the fonts of each part of echarts one by one through the theme（recommend）

This method is more expensive, but the operation is the most transparent, and it is also convenient if you want to integrate other fonts later.

I recommend the third

[hustcc]

Why not plan 2？I just want a Han font as default.

[BQXBQX]

Why not plan 2？I just want a Han font as default.

I think it's not very good in terms of semantics. Source Han is a specific font, while sans serif is a type, which is somewhat conflicting in terms of semantics.

In fact, I think the best way is to make napi canvas support Chinese fonts, but I see that the iteration speed of napi canvas is very slow, so I want to try a folk version and solve this problem by reading its source code. And if there are other new requirements for napi canvas later, for example, if g2 needs to use it and encounters problems, we can also solve and handle it by ourselves.

[BQXBQX]

I briefly researched skia, the 2D rendering library that @napi/canvas relies on, and concluded that even if the source code is modified, it is not possible to customize itself to support Chinese fonts 😭. Skia is not cairo, and it will not look for font files from the operating system for rendering. Its purpose is cross-platform and zero dependency, so fonts must be registered by yourself, especially complex fonts like Chinese, which have a heavy dependency. So there are only the second and third options.

[hustcc]

I think both methods are acceptable:

1. Submit a PR to them and try to resolve it quickly.
2. Use plan 2 as a quick temporary fix, then migrate after the official resolution.

Forking and maintaining is not considered.

[BQXBQX]

I think both methods are acceptable:

1. Submit a PR to them and try to resolve it quickly.
2. Use plan 2 as a quick temporary fix, then migrate after the official resolution.

Forking and maintaining is not considered.

I think the second one is the best way 🤔. I will push my code tomorrow.