fix: remove non-standard module export condition

[pi0]

🔗 Linked issue

resolves #1558

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

module is a non-standard export condition not supported by Node.js or any runtimes which was previously used as a top-level property in order to help bundlers pick the esm-like/browser builds.

We disabled top level module field long before because of this externals, new resolution conditions in #1401 added it back and makes issues with packages such as ts-lib and @sanity/client that are (wrongly!) using AND preferring this export condition over `import.

I also updated Bun conditions. Checking their docs, it seems they recently made same decition.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[danielroe]

Nice work 👌

[codecov]

Codecov Report

Merging #1559 (fd9c76b) into main (7fa8408) will decrease coverage by 0.01%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main    #1559      +/-   ##
==========================================
- Coverage   76.49%   76.48%   -0.01%     
==========================================
  Files          73       73              
  Lines        7580     7579       -1     
  Branches      751      751              
==========================================
- Hits         5798     5797       -1     
  Misses       1781     1781              
  Partials        1        1              

Files Changed	Coverage Δ
src/rollup/config.ts	90.60% <0.00%> (ø)
src/options.ts	96.64% <100.00%> (ø)
src/presets/bun.ts	100.00% <100.00%> (ø)