Replace parquetjs for better deno compatibility?

[canadaduane]

Currently, when adding npm:together-ai to a deno project, the following warnings are shown:

$ deno add npm:together-ai
Add npm:together-ai@0.10.0
Warning The following packages contained npm lifecycle scripts (preinstall/install/postinstall) that were not executed:
┠─ npm:lzo@0.4.11
┃
┠─ This may cause the packages to not work correctly.
┠─ Lifecycle scripts are only supported when using a `node_modules` directory.
┠─ Enable it in your deno config file:
┖─ "nodeModulesDir": "auto"
Warning The following packages contained npm lifecycle scripts (preinstall/install/postinstall) that were not executed:
┠─ npm:lzo@0.4.11
┃
┠─ This may cause the packages to not work correctly.
┠─ Lifecycle scripts are only supported when using a `node_modules` directory.
┠─ Enable it in your deno config file:
┖─ "nodeModulesDir": "auto"

As far as I can tell, lzo is unnecessary, and exists only because it is a transitive dependency of parquetjs, which hasn't been maintained in 5 years or so. It uses a node-gyp build pipeline to add a few C functions for fast LZO compression/decompression.

Possible fixes:

• replace parquetjs with @dsnp/parquetjs: this package seems to be maintained and appears to cover the needs of together-ai afaict. Note that they explicitly removed lzo some time ago due to the compress/decompress tests not passing, which may also be true of parquetjs: LZO and LZO_RAW Support LibertyDSNP/parquetjs#18
• replace parquetjs with parquetjs-lite: this package does not look maintained, like parquetjs, but it does not have a dependency on lzo.

The only functionality that might depend on lzo is the upload function for uploading fine tunes. Some testing might be needed to confirm that it works as expected, once one of the above two replacements is made.

Fixing this would make users of together-ai in the deno ecosystem happy and would offer confidence that "everything works fine" rather than a few scare warnings.

[mdouglass]

I'll add to this that parquetjs is problematic on the npm/node.js side as well since it transitively brings in q which is deprecated:

npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead

[platypii]

Would be fixed by my PR #105 but I have been unable to get reviews