fix: update unbuild to 2.0.0, fix type declarations for ESM

[wojtekmaj]

Fixes #24

This PR:

• Updates unbuild to v2.0.0 as this is the release that includes the feature that enables us to fix the issue "This expression is not callable." when using TypeScript with moduleResolution set to node16 or nodenext #24 in the first place.
• Switches from declaration: true to new declaration: 'compatible' to generate both declaration files
• Removes (!) exports["."].types, as that mapped same declaration file (CJS one!) to both CJS and ESM entry file.

Before:

After:

[bluwy]

The build fails for me locally:

> @vitejs/[email protected] build /Users/bjorn/Work/oss/vite-plugin-basic-ssl
> unbuild && esno scripts/patchCJS.ts

ℹ Building plugin-basic-ssl                                                               2:58:42 PM
ℹ Cleaning dist directory: ./dist                                                         2:58:42 PM
Entry module "src/index.ts" is using named and default exports together. Consumers of your bundle will have to use `chunk.default` to access the default export, which may not be what you want. Use `output.exports: "named"` to disable this warning.
✔ Build succeeded for plugin-basic-ssl                                                    2:58:43 PM
[2:58:43 PM]   dist/index.cjs (total size: 1.86 kB, chunk size: 1.86 kB, exports: default, getCertificate)

[2:58:43 PM]   dist/index.mjs (total size: 1.54 kB, chunk size: 1.54 kB, exports: default, getCertificate)

Σ Total dist size (byte size): 1.18 MB
                                                                                           2:58:43 PM
dist/index.cjs CJS patch failed
 ELIFECYCLE  Command failed with exit code 1.

It looks like our CI didn't run the build at all since Vitest can run on raw files.

[wojtekmaj]

This was because the code we generated was ES3 (!) compliant, and using new unbuild, it's not doing that by default. It all comes down to this setting:

https://rollupjs.org/configuration-options/#output-generatedcode-reservednamesasprops

Fixed that, patch now works.

[bluwy]

Thanks for looking into this! That makes sense to me.

@patak-dev I guess we should release this as a minor as it could affect things? Don't think it needs a major though since things should still work the same.