[Feature Request]: Support for uploading Zapier integrations of type Module

[arcticfly]

Current Behavior

After running zapier init --template=typescript zapier-app, I've modified the following two files:

package.json

...
"type": "module",
...

and

tsconfig.json

...
"module": "ESNext",
"moduleResolution": "Bundler",
...

When I now run zapier validate, I see an error related to running the zapier cli with a project of type module:

zapier validate
Validating project locally
(node:64821) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 ›   Error: require() of ES Module /path/test-zapier-app/example-app/index.js from
 ›   /Users/user/.nvm/versions/node/v21.6.2/lib/node_modules/zapier-platform-cli/src/utils/local.js not supported.
 ›   index.js is treated as an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which declares all .js files in that package scope as ES modules.
 ›   Instead either rename index.js to end in .cjs, change the requiring code to use dynamic import() which is available in all CommonJS modules, or change "type": "module" to "type": "commonjs" in
 ›   /path/test-zapier-app/example-app/package.json to treat all .js files as CommonJS (using .mjs for all ES modules instead).
 ›
 ›
 ›   re-run this command with `--debug` for more info

Other zapier CLI commands result in similar errors.

Desired Behavior / Feature Request

All zapier CLI commands work with projects of type "module".