Fix types, better exports and use tsup for build, remove parcel

[sneridagh]

We are having problems in some setups in macos where parcel errors with a segmentation fault and we found also some weird errors related with it in pnpm lock, where the lock keeps updating because of it (apparently, their entries in the lock keep cycling infinitely). In addition, the resultant code has some weird names with a looong hash that end up in the dev tools. Then I also learned that tsup is more pure with their outputs and it was the recommended setup, see:

https://www.totaltypescript.com/how-to-create-an-npm-package

Totally worth it from top to bottom.

I also fixed the remaining types that forced us to ||true in the build output. So overall this PR improves the current situation, in a non-breaking way.

[netlify]

✅ Deploy Preview for plone-components canceled.

Name	Link
🔨 Latest commit	4ac8e2e
🔍 Latest deploy log	https://app.netlify.com/sites/plone-components/deploys/6729072b1deec6000843f296

[davisagli]

Could you explain more about the switch from parcel to tsup? What's the motivation and are there any tradeoffs?

[sneridagh]

@davisagli just added some more background in the description.

[stevepiercy]

Was parcel something the developer directly called? If so, does its replacement merit more than a change log entry?

[sneridagh]

@stevepiercy no, always in automated build processes, but they could see when it failed.

[sneridagh]

BTW, @davisagli @stevepiercy in the next days, probably I will be replacing (if possible) parcel with tsup in all our builds

[davisagli]

I'm not really qualified to review the Node/Typescript details here. I'm okay with it as long as there isn't an impact for users.