Support for proxy and custom certificate configuration

[ricOC3]

Motivation

When using the TinyMist Typst VSCode extension in a proxy environment, I encountered an issue where document preview fails with the following error:

typst_ts_compiler error: failed to download package: error trying to connect: invalid peer certificate: UnknownIssuer

This issue hinders the use of the extension in environments with strict network security, such as corporate networks.

Description

The issue appears to be related to certificate verification in a proxy environment. A similar problem has been reported in the Typst repository (see Typst Issue #1678), where the solution involved allowing environment variables or CLI arguments to bypass the certificate verification.

It would be beneficial if the TinyMist Typst extension could also support similar options, enabling users to configure the extension for proxy environments where certificate verification might fail.

Examples/Questions

• Is it possible to implement the support for environment variables or CLI arguments in TinyMist Typst to handle certificate verification issues in proxy environments?
• Would this feature allow users to set specific proxy-related configurations that could resolve this error?

Finally, this is my first time posting an issue, so I apologize if there are any mistakes or if I've overlooked anything.

Thank you for your time and for developing such a helpful tool!