fix: list types first in package exports

[timostroehlein]

According to Node.js documentation the types should always be listed first when using package exports, see:
https://nodejs.org/api/packages.html#community-conditions-definitions

This also fixes an issue with eslint-plugin-import throwing a warning Parse errors in imported module 'zx': parserPath or languageOptions.parser is required! (undefined:undefined) due to the wrong order of package exports.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[antongolub]

I believe this is true, but I don't want it to be so. Ordered unordered collection is pure madness.

An object is a member of the type Object. It is an unordered collection of properties each of which contains a
primitive value, object, or function. A function stored in a property of an object is called a method.