feat: Add ECMAScript 6 (ES6) support

[dplewis]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

The code base doesn't support async/await since babel didn't support it in the runtimegenerator. We could update babel but I don't think project needs to be trancompiled. The test suite ran against /src instead of /lib so this error didn't get caught

*/node_modules/@parse/push-adapter/lib/WEB.js:59
var _ref = _asyncToGenerator( /#PURE/regeneratorRuntime.mark(function _callee(data, devices) {
^

Closes: #256

Approach

• Add "type": "module" to package.json to enable ES6
• Remove babel transcompiler
• Remove unused files
• Randomize test suite
• Use C8 for test coverage
• Bump testing dependencies
• Improve CI npm cache

TODOs before merging

• Add tests
• Add entry to changelog
• Add changes to documentation (guides, repository pages, in-code descriptions)

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.10%. Comparing base (915d9af) to head (43a9b47).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     parse-community/Parse-SDK-JS#255      +/-   ##
==========================================
- Coverage   91.78%   90.10%   -1.68%     
==========================================
  Files           8        8              
  Lines         499     1274     +775     
==========================================
+ Hits          458     1148     +690     
- Misses         41      126      +85     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[parseplatformorg]

🎉 This change has been released in version 6.3.0

[Moumouls]

Not sure to understand why it was switched to ESM since Parse Server is not a module and there is plenty of issues with ESM currently waiting for NodeJS in node 23-24 fix.

On my side Jest is failing due to ESM in CommonJs project.

Parse custom ESM detection fail for example in jest since JEST return a custom error when you try to import an ESM in Common JS. I'll fix my fork to support the jest error, a dedicated PR should be done on parse for proper ESM detection

[Moumouls]

it seems that jest just exit if he detect ESM in commonjs, so the error detection don't work

[mtrezza]

Are you referring to the CI tests? They seem to work.