feature: Support Deno

[airtonix]

This largely means that all the packages should be esm and usable via cdns like https://esm.sh.

We shouldn't rely on transforms that involve babel or custom typescript loaders.

finally, since we're writing esm deployment shouldn't require any use of webpack/vite/parcel. The deno ecosystem already has tools that handle this unlikely scenario.