chore: changed rollup config to support dynamic imports in react native

[ignaciosantise]

Description

Changed rollup config to enable dynamic imports on react native

Type of change

• Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

Tested locally on iOS and Android emulators

Checklist

• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

Additional Information (Optional)

⚠️ Not tested on web

---

Note

Restructures Rollup to emit ESM/CJS/UMD bundles, adds .native resolution for React Native, and applies env-aware optimizations.

• Build Outputs:
  • Split into distinct builds: es → ./dist/index.js, cjs → ./dist/index.cjs, umd → ./dist/index.umd.js.
  • external: packageDependencies for all builds; ES sourcemaps now hidden in production; ES output compacted in production.
• Module Resolution:
  • nodeResolve now resolves ".ts", ".js", ".native.ts", ".native.js" with browser: true.
• Bundling/Transpile:
  • commonjs configured for mixed ESM and to ignore dynamic requires; esbuild targets es2020, enables tree-shaking, removes legal comments, and drops console/debugger in production.
• Tooling:
  • visualizer runs only in non-production builds.

^{Written by Cursor Bugbot for commit 4eeb14f. This will update automatically on new commits. Configure here.}