Rework to remove need for js-dist

[tstirrat15]

It'd be nice to only have a single package.json as a single source of truth. There are other node libraries out there that are written in TS and distributed in JS; https://github.com/nats-io/nats.node is an example.

[tstirrat15]

I think authzed-node should work fine for a non-TS consumer. I'm going to verify that before I cut it out, though. My understanding is that it was added when a user asked for it for a non-TS environment.

[tstirrat15]

This is almost certainly why: https://github.com/authzed/authzed-node/blob/main/package.json#L31-L32

Part of this work will be figuring out why protobuf-ts has its own runtime :thonk:

[tstirrat15]

Might be worth seeing if tsup could improve our build process as well.

[tstirrat15]

Another thought:

There are libraries that ship multiple entrypoints, such that you do:

import { SomeThing } from 'my-library';
import { SomeOtherThing } from 'my-library/other';

The thought is that we'd have one set of client library files, and then two backing implementations. I think it makes an assumption that the TS proto gencode and the non-TS proto gencode look the same, though, which isn't necessarily going to be the case.