fix: replace neon-js with neon-core and neon-api dependencies

[raulduartep]

Since neon-js bundles its dependencies into a single file (index.js), it becomes impossible to patch specific libraries. For example, if you try to patch the noble/hashes package to use a native version in React Native, neon-js won’t use the patched version because it relies on its own bundled copy of the library.

Another issue this causes is TypeScript conflicts with types exported by neon-core. For example, if an app uses neon-dappkit and also depends on neon-core, both versions must match exactly. Even if you try to enforce this with overrides, it won’t work properly because neon-dappkit depends on neon-js, which bundles its own version of neon-core instead of using the one installed in the app.

I also removed the browser field from package.json, since it’s important to let consumers decide which patches or polyfills to use. For example, in React Native it’s better to use react-native-quick-crypto instead of crypto-browserify.

[luc10921]

Why are you removing those rules?

[raulduartep]

These rules were added when I updated the typescript-eslint library. To avoid changing a large portion of the codebase, I’ve disabled them.

[raulduartep]

I've closed this PR since it does not seems to fix the main problem with neon-js. I noticed that neon-core also bundle all dependency into it's bundle file.