Spike: Switch from lerna to pnpm workspaces

Nessuno ha ancora preso questa issue.

Our current lerna-based setup is very inefficient. Most of the pull requests in this repository are created by RenovateBot to update package-lock files, our git history is full of RenovateBot commits that make it difficult to spot relevant changes.

Let's investigate how to switch from lerna to [pnpm](https://pnpm.js.org/) and use a single root package-lock file for the entire monorepo.

References:
- pnpm workspaces: https://pnpm.js.org/en/workspaces
- Travis CI setup: https://pnpm.js.org/en/continuous-integration#travis

Topics to investigate:
- How to release new versions using conventional release process? Can we perhaps use https://github.com/atlassian/changesets? Related: https://github.com/pnpm/pnpm/issues/2225
- Does RenovateBot support pnpm? If not, is there any other bot we could use instead? E.g. GitHub's [Dependabot](https://github.com/dependabot). Related: https://github.com/renovatebot/renovate/issues/2015

Inizia dai riferimenti a pnpm workspaces e Travis CI nell’issue, quindi esamina gli attuali workflow di Lerna, package-lock, RenovateBot e delle release. Il lavoro è completato quando viene documentato un piano di migrazione attuabile, che includa la gestione delle release e il supporto agli aggiornamenti delle dipendenze, anziché apportare una modifica all’implementazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.