feat: export createAxiosLanguageModel

[abichinger]

Exporting createAxiosLanguageModel would solve the following problems

1. support custom axios config (e.g. users can pass a proxy)
   related: Support axios config #73 Add HTTP_PROXY variable and proxy process when access endpoints' api services #55 feat: add request config #34
2. ability to pass custom parameters to the endpoint /v1/chat/completions

[DanielRosenwasser]

Personally I don't think the library should expose Axios at all, since it's an internal implementation detail.

For example, in another issue someone asked about how to take advantage of streaming responses from OpenAI. Best I can tell, Axios doesn't make that easy to do (or it might not provide the APIs to do so at all). I use this as a specific example, but my point is really that hooking up Axios or whatever language model provider API is easy enough because TypeChatLanguageModel just needs a single function at the moment.

Still, I'll let others weigh in here.

[snewell92]

@DanielRosenwasser thete are likely legit n/w level overrides desired, but middleware is likely the better way forward imo rather than anything axios/fetch/ky specific.

I agree with exposing the model the way it is with the single function 👍

[Akimyou]

I don't think TypeChat needs to provide proxy settings, as it can support proxy access through higher-level configurations, such as proxychains4.

[moltar]

1. I think the package shall use undici as this will be the default client in the future Node versions
2. If anything needs to be exposed, then I think FetchEsque types from trpc can be borrowed, which can adapt to any fetch implementation.