fix: Revert parquet-wasm integration

[ibgreen]

Revert Parquet WASM integration due to overwhelming bundling issues.
For some reason the browser file replacement for the wasm loader wasn't taking effect and the node wasm still kept being imported. It could be a stupid typo, but running out of time to fight this and we need to cut a new release.

[kylebarron]

I haven't tried to export both of them at the same time. I use the node export in tests and the esm export in the browser, which have both worked well for me. (note, IIRC this uses the undocumented esm2 entry point, which removes import.meta.url, which I think was giving some sort of error previously in loaders)

[ibgreen]

Any chance you could use a nestedexports field in package.json to export the appropriate version for browser&node and esm&commonjs? I think it would save a lot of grief in apps that try to use this.

https://webpack.js.org/guides/package-exports/#target-environment

You could also add explicit entry points for people who want to cherry-pick or use the experimental versions.

https://github.com/visgl/loaders.gl/blob/master/modules/parquet/package.json#L25

[kylebarron]

Can you try 0.6.0-beta.1 with kylebarron/parquet-wasm#382